Enforced Unitasking in Multitasking Systems

ABSTRACT

A computer system includes one or more devices that are capable of multitasking (performing at least two tasks in parallel or substantially in parallel). In response to detecting that one of the devices is performing a first one of the tasks, the system prevents the devices from performing at least one of the tasks other than the first task (such as all of the tasks other than the first task). In response to detecting that one of the devices is performing a second one of the tasks, the system prevents the devices from performing at least one of the tasks other than the second task (such as all of the tasks other than the first task).

BACKGROUND

Today's computer users are faced with a continuous barrage of incominginformation in the form of email messages, text messages, voice messagesand live voice calls, and messages transmitted via social networkingsystems, to name a few. Similarly, users are expected and sometimesrequired to create and transmit an equally high volume of outgoingmessages as part of their work and social commitments. Such a constantstream of communication can make it difficult for computer users toconcentrate on tasks requiring deep, sustained thought while usingcomputers.

Although many recognize the potential harm of increasingly distractedcomputer and Internet use, as evidenced by pejorative terms such as“Crackberry addict” to describe someone who compulsively sends andreceives email using a Blackberry mobile computing device, the blame forsuch harms typically is laid at the feet of the computer user forfailing to exercise sufficient self-control. The solution most commonlyproposed to this problem is for computer users to unilaterally changetheir usage habits, such as by leaving their computers at home while onvacation or manually turning off their smartphones while in restaurants.

SUMMARY

A computer system includes one or more devices that are capable ofmultitasking (performing at least two tasks in parallel or substantiallyin parallel). In response to detecting that one of the devices isperforming a first one of the tasks, the system prevents the devicesfrom performing at least one of the tasks other than the first task(such as all of the tasks other than the first task). In response todetecting that one of the devices is performing a second one of thetasks, the system prevents the devices from performing at least one ofthe tasks other than the second task (such as all of the tasks otherthan the first task).

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1A is a dataflow diagram of a computer control system according toone embodiment of the present invention;

FIGS. 1B-1D are diagrams illustrating profiles and relationships amongprofiles according to embodiments of the present invention;

FIG. 1E is a diagram illustrating relationships between profiles andlogic modules according to one embodiment of the present invention;

FIGS. 1F-1G are diagrams illustrating the operation of a profilecontroller according to one embodiment of the present invention;

FIGS. 1H-1I are diagrams illustrating the operation of a logic modulecontroller according to one embodiment of the present invention;

FIG. 1J is a diagram illustrating the operation of a logic moduleexecution unit according to one embodiment of the present invention;

FIG. 1K is a diagram illustrating the operation of a profile executionunit according to one embodiment of the present invention;

FIG. 2 is a diagram of a context controller for obtaining andsynthesizing context data according to one embodiment of the presentinvention;

FIG. 3A is a flowchart of a method performed by the system of FIG. 1Faccording to one embodiment of the present invention;

FIG. 3B is a flowchart of a method performed by the system of FIG. 1Gaccording to one embodiment of the present invention;

FIG. 3C is a flowchart of a method performed by the system of FIG. 1Haccording to one embodiment of the present invention;

FIG. 3D is a flowchart of a method performed by the system of FIG. 1Iaccording to one embodiment of the present invention;

FIG. 3E is a flowchart of a method performed by the system of FIG. 1Jaccording to one embodiment of the present invention;

FIGS. 3F and 3G are flowcharts of methods performed by the system ofFIG. 1K according to embodiments of the present invention;

FIG. 4A is a diagram of a computer control system implemented on asingle device according to one embodiment of the present invention;

FIG. 4B is a diagram illustrating a physical implementation of deviceprofiles according to one embodiment of the present invention;

FIG. 4C is a diagram illustrating a physical implementation of userprofiles according to one embodiment of the present invention;

FIGS. 5A-5D are diagrams illustrating the use of activation states withprofiles and logic modules according to embodiments of the presentinvention;

FIGS. 6A-6D are flowcharts of methods performed to execute profiles andlogic modules according to embodiments of the present invention;

FIG. 7A is a diagram illustrating use of an embodiment of the presentinvention to enforce communication unitasking among one or more devicesaccording to one embodiment of the present invention;

FIG. 7B is a diagram illustrating use of an embodiment of the presentinvention to enforce unitasking among one or more devices according toone embodiment of the present invention;

FIG. 7C is a diagram illustrating a plurality of unitasking specifiersaccording to one embodiment of the present invention;

FIG. 8A is a flowchart of a method performed by the system of FIG. 7Aaccording to one embodiment of the present invention;

FIG. 8B is a flowchart of a method performed by the system of FIG. 7Baccording to one embodiment of the present invention; and

FIGS. 9A-9D are illustrations of user interfaces for interacting withprofiles and logic modules according to one embodiment of the presentinvention.

DETAILED DESCRIPTION

Referring to FIG. 1A, a dataflow diagram is shown of a computer controlsystem 100 implemented according to one embodiment of the presentinvention. In general, the system 100 includes one or more profiles thatdefine actions to be taken by the system 100 in response to satisfactionof conditions defined by the profiles. As will be described in moredetail below, such conditions and actions may be defined in ways thatcontrol the extent to which users of the system 100 are distracted bydevices within the system 100 and by other devices used by such users.

The system 100 includes one or more logic modules 102 a-c. Althoughthree logic modules 102 a-c are shown in FIG. 1A as an example, thesystem 100 may include any number of logic modules. In general, each ofthe logic modules 102 a-c defines a condition and a correspondingaction. As will be described in more detail below, the system 100 orother embodiment of the present invention may perform the action definedby a logic module if the condition defined by the logic module issatisfied by the current context of the system 100. For example, logicmodule 102 a includes condition specifier 104 a (which specifies a firstcondition) and action specifier 106 a (which specifies a first action);logic module 102 b includes condition specifier 104 b (which specifies asecond condition) and action specifier 106 b (which specifies a secondaction); and logic module 102 c includes condition specifier 104 c(which specifies a third condition) and action 106 c (which specifies athird action).

The condition and action specified by a particular logic module mayimplement a rule, such that the system 100 necessarily performs theaction in response to determining that the condition is satisfied. Logicmodules 102 a-c need not, however, implement rules. Alternatively, forexample, logic modules 102 a-c may implement statistical methods suchthat the action specified by a logic module may or may not be performedin response to detecting that the condition specified by the logicmodule is satisfied in a particular instance. For example, a logicmodule may be implemented such that the action specified by the logicmodule is performed with a likelihood of 50% in response to determiningthat the condition specified by the logic module is satisfied, with thedecision in a particular instance being implemented using apseudo-random number generator. Various examples disclosed herein,however, will describe logic modules 102 a-c as implementing rules forease of explanation.

Each of condition specifiers 104 a-c may specify a simple condition,such as a condition including only a single premise, such as“TIME=11:00,” or a complex condition including a plurality of premisesjoined by one or more Boolean operators (e.g., AND, OR, XOR, NOT) in anycombination. Therefore, any reference herein to a “condition” includessimple conditions and/or complex conditions. More generally, a conditionmay be implemented using any process that produces an output (e.g., abinary output) to determine whether to perform the corresponding action.

Similarly, each of actions 106 a-b may specify a simple action, such asan action to block receipt of an email message, or a complex actionincluding a plurality of actions. Therefore, any reference herein to an“action” refers includes simple actions and/or complex actions. Moregenerally, an action may be implemented using any process.

An action specifier may specify an action at any level of generality.For example, an action specifier may specify a particular action to beperformed by the hardware of a device. As another example, an actionspecifier may specify a type of action, such as “block.” In such a case,the specified action may be performed by identifying one or morespecific acts that implement the specified action, and by performing theone or more specific acts. For example, a “block” action may beperformed by performing a first set of acts to block an incoming emailmessage, by performing a second set of acts to block an outgoing emailmessage, and a third set of acts to block an incoming voice call, wherethe first, second, and third sets of acts differ from each other. Theparticular act(s) to perform in a particular instance to implement the“block” action may be determined dynamically and on-the-fly.

More generally, an action specifier may specify an action that isdefined by any process, function, algorithm, or other set of acts. Forexample, an action specifier may specify a process which, whenperformed, receives input from some or all of the context data describedbelow. As a result, the acts performed when executing a particularaction specifier may vary from case to case depending on the currentcontext data.

Any two of the condition specifiers 104 a-c may specify the same ordifferent conditions from each other. Similarly, any two of the actionspecifiers 106 a-c may specify the same or different actions from eachother. For example, no two of the condition specifiers 104 a-c mayspecify the same condition as each other. As another example, conditionspecifiers 104 a and 104 b may specify the same conditions as eachother, but condition specifier 104 c may specify a condition thatdiffers from the conditions specified by condition specifier 104 a andcondition specifier 104 b. Similarly, for example, no two of the actionspecifiers 106 a-c may specify actions that are the same as each other.As another example, action specifiers 106 a and 1046 b may specify thesame actions as each other, but action specifier 106 c may specify anaction that differs from the actions specified by both action specifier106 a and action specifier 106 b.

The system 100 also includes various profiles. In general, the term“profile” is used herein to refer to any set of data, such as a set ofdata that includes parameters, where each parameter has both a type anda value. For example, one parameter may have a type of “time” and avalue that represents the current time (e.g., 11:00).

The system 100 includes, for example, one or more system profiles. Ingeneral, a system profile includes data representing information relatedto the system 100 as a whole. A single system profile 110 is shown inFIG. 1A. The system 100 may, however, include more than one systemprofile.

The system 100 also includes, for example, one or more user profiles. Ingeneral, a user profile includes data representing information relatedto a particular human user. In the example of FIG. 1A, the system 100includes two user profiles 112 a and 112 b, which include datarepresenting information related to users 122 a and 122 b, respectively.The system 100 may, however, include any number of user profiles.

The system 100 also includes, for example, one or more device profiles.In general, a device profile includes data representing informationrelated to a particular device, such as a computing device or acommunication device. In the example of FIG. 1A, the system 100 includesthree device profiles 114 a-c, which include data representinginformation related to devices 124 a-c, respectively. The system 100may, however, include any number of device profiles.

The system 100 need not include all of the types of profiles shown inFIG. 1A, where examples of profile types are system, user, and device.Rather, for example, the system 100 may solely include one or moreprofiles of a single type. For example, the system 100 may solelyinclude a system profile, or solely include a user profile, or solelyinclude a device profile. More generally, the system 100 may include oneor more profiles of each of one or more of the types shown in FIG. 1A,so that the system 100 includes at least one profile of at least onetype.

Profiles may be associated with each other in various ways. For example,a system profile may be associated with one or more user profiles.Referring to FIG. 1B, an example is shown in which system profile 110 isassociated with user profiles 112 a and 112 b, as indicated byassociations 130 a and 130 b, respectively. Although in the example ofFIG. 1B the system profile 110 is associated with all of the userprofiles 112 a-b in the system 100, this is not required; the systemprofile 110 may alternatively be associated with fewer than all of theuser profiles 112 a-b in the system 100.

Referring to FIG. 1C, an example is shown in which: (1) user profile 112a is associated with device profiles 114 a and 114 b, as indicated byassociations 132 a and 132 b, respectively; and (2) user profile 112 bis associated with device profile 114 c, as indicated by association 132c. As these examples illustrate, a user profile may be associated withany number of device profiles. Furthermore, although not shown in FIG.1C, two user profiles may be associated with the same device profile.For example, this would occur in FIG. 1C if the user profile 112 b wereadditionally associated with device profile 114 b.

Referring to FIG. 1D, an example is shown in which system profile 110 isassociated with device profiles 114 a-c, as indicated by associations134 a-c, respectively. Although in the example of FIG. 1D the systemprofile 110 is associated with all of the device profiles 114 a-c in thesystem 100, this is not required; the system profile 110 mayalternatively be associated with fewer than all of the device profiles114 a-b in the system 100.

Any profile of any type may be associated with more or more logicmodules. For example, referring to FIG. 1E, an example is shown in whichsystem profile 110 is associated with logic module 102 a (as indicatedby association 136 a); user profile 112 a is associated with logicmodule 102 a (as indicated by association 136 b) and logic module 102 b(as indicated by association 136 c); user profile 112 b is associatedwith logic module 102 c (as indicated by association 136 d); deviceprofile 114 a is associated with logic module 102 a (as indicated byassociation 136 e); device profile 114 b is associated with logic module102 a (as indicated by association 136 f) and logic module 102 c (asindicated by association 136 g); and device profile 114 c is notassociated with any logic module.

As illustrated in FIG. 1E, any profile of any type may be associatedwith any number (i.e., zero or more) of logic modules. One logic modulemay be associated with multiple profiles, e.g., multiple profiles of thesame type or of different types. Furthermore, although in the example ofFIG. 1E at least one profile of each type (system, user, and device) isassociated with at least one logic module, this is not a requirement.Instead, for example, the system profile 110 may not be associated withany of the logic modules 102 a-c. As another example, neither of theuser modules 112 a-b may be associated with any of the logic modules 102a-c. As yet another example, none of the device modules 114 a-c may beassociated with any of the logic modules 102 a-c. All that is requiredis that at least one profile in the system 100 be associated with atleast one of the logic modules 102 a-c.

Referring to FIG. 2, a dataflow diagram is shown of a system 200 forobtaining and storing context data 202. Context data 202 is alsoreferred to herein as “context.” Context data 202 may, for example,represent information about an activity currently engaged in by one ofthe users 122 a-b of the system 100, information about appointments on auser's calendar, or information about messages currently beingtransmitted by the system 100.

The system 200 includes a plurality of context sensors 206 a-j. Ingeneral context sensors 206 a-j obtain sensor inputs 214 a-j,respectively, and generate outputs 208 a-j, respectively. The outputs208 a-j of context sensors 206 a-j are provided to and received bycontext controller 204, which generates and stores context data 202based on the received outputs 208 a-j. Context data 202 may, forexample, include a context data record 210 a, which includes fields 212a-j corresponding to and representing sensor outputs 208 a-j,respectively. More specifically, field 212 a may represent sensor output208 a, field 212 b may represent sensor output 208 b, and so on.

Although not shown in FIG. 2, context controller may be used to read thecontext data 202. For example, context controller 204 may provide outputrepresenting some or all of context data 202, e.g., in response to arequest from another component for such data. Furthermore, contextcontroller 204 may receive a request from another component to modifysome or all of context data 202 and, in response to such a request, maymake the requested modification to the context data 202.

Context controller 204 may sample the outputs 208 a-j repeatedly, e.g.,periodically (e.g., every millisecond, every second, or every minute),or in response to detecting a change in one or more of the outputs 208a-j. The context controller 204 may generate and store multiple contextdata records 210 a-n, each of which represents a distinct sample of someor all of the sensor outputs 208 a-j. Such repeated sampling and storagemay, for example, be used to store a record of the history of contextdata generated by the context controller 204 within the context data 202itself. Alternatively, for example, the context controller 204 may storeonly a single context data record 212 a within the context data 202, andoverwrite the values in the context data record 212 a based on theoutputs 208 a-j received most recently from the sensors 206 a-j.

Each of the sensors 206 a-j may provide, as its output, an output thatis identical to or a copy of the sensor's input, or an output that isgenerated based on the sensor's input but which differs from thesensor's input in any of a variety of ways, such as in its format and/orvalue. Furthermore, inputs 214 a-j are optional; they may be omittedfrom the system 200 or integrated into their corresponding sensors. Anyone or more of the sensors 206 a-j may receive multiple inputs andderive output from such multiple inputs in any way.

Sensor 206 a is a time sensor, which receives time sensor input 214 a,such as data generated by a clock representing a current time. Timesensor 206 a may, for example, generate output 208 a representing acurrent time (e.g., the time at or around the time at which the sensoroutput 208 a is generated). Such a time may be any kind of time, such asa real time (e.g., Jan. 1, 2011 at 11:00 AM) or a system time (e.g., anumber of clock cycles since a device was booted), represented to anydegree of accuracy.

Storing a value that is equal to or based on the time sensor output 208a in the context records 210 a-n effectively marks such records withtimestamps that may later be used to associate any particular recordwith the time stored in the record's time field 212 a, which mayrepresent the actual or approximate time at which the record wascreated. The context controller 204 may sample all of the sensor outputs208 a-j at or near the time represented by the time sensor output 208 aand generate a corresponding context record based on such sampledoutputs, so that each of the context records 212 a-n generated by thecontext controller 204 a contains data representing context informationthat is valid for a single point in time or a relatively short period oftime overlapping with or near the time represented by the record's timefield 212 a, and so that the record's time field 212 a may subsequentlybe used to identify the actual or approximate time(s) for which theinformation represented by the other fields 212 b-i in the same recordis valid.

Any references below to the “current sample period” in connection withthe set of sensor outputs 208 a-j therefore refers to a point in time orperiod of time defined by reference to the time represented by timesensor output 208 a, such as the exact point in time represented by timesensor output 208 a or a time period beginning with or otherwiseincluding the point in time represented by time sensor output 208 a.Similarly, any use of the terms “current” or “currently” below should beunderstood to refer to a time or time period defined by reference to thetime represented by the time sensor output 208 a. For example, in thecontext of a particular set of sensor outputs 208 a-j within the currentsample period, “the current user” should be understood to refer to theuser represented by output 208 b of user sensor 206 b at or around thetime represented by time sensor output 208 a.

Sensor 206 b is a user sensor, which receives user sensor input 214 band generates, based on input 214 b, output 208 b representing a user,such as a current user of one of the devices 124 a-c or the system 100as a whole. The sensor 206 b may, for example, obtain input 214 brepresenting user login credentials (e.g., username and/or password) orbiometric information, and provide user output 208 b uniquelyidentifying the user specified by the input to the sensor 206 b. Theuser output 208 b is not limited to output representing the identity ofthe user, but more generally may represent any data relating to theuser.

Sensor 206 c is a device sensor, which receives device input 214 c andgenerates, based on input 214 c, output 208 c representing a device,such as one of the devices 124 a-c of the system 100. The device output208 c during a particular sample period may, for example, represent adevice currently used by the user represented by the output 208 b ofuser identification sensor 206 b during the sample period. The devicesensor 206 c may, for example, obtain input 214 c representing a deviceserial number or other unique identifier of the device, and providedevice output 208 c uniquely identifying the device. The device output208 c is not limited to output representing the identity of the device,but more generally may represent any data relating to the device, suchas data representing any aspect of the device's current configuration,such as audio volume, screen brightness, and whether any particularinput or output components of the device currently are enabled ordisabled.

Sensor 206 d is an application sensor, which receives application input214 d and generates, based on input 214 d, output 208 d representing thestate of one or more software applications (which includes any kind ofsoftware, such as operating systems, application programs, and web-basedapplications). For example, the application sensor output 208 d during aparticular sample period may, for example, represent the state of one ormore software applications executing on a device. The application output208 d during a particular sample period may, for example, represent thestate of one or more software applications executing on the devicerepresented by the output 208 c of device sensor 206 c, or the state ofone or more software applications being executed by or on behalf of theuser represented by the output 208 b of the user sensor 206 b, duringthe same sample period. The application sensor output 208 d may, forexample, indicate which applications currently are executing, whichapplication(s) is/are in the foreground, which application has the inputfocus, which application(s) currently is/are providing user output, andwhich application(s) currently is/are receiving user input. Theapplication sensor 206 d may obtain input 214 d from any source, such asan operating system of the device represented by device sensor output208 c, or from applications by using application program interface (API)calls to such applications.

Sensor 206 e is a message sensor, which receives message input 214 eand, based on input 214 e, generates output 208 e representinginformation relating to one or more messages. Output 208 e may, forexample, represent a communication mode of the message (e.g., whetherthe message is an email message, a text message, or a live voice call),data from the message (such as the body of an email message, audio froma voice call, or text transcribed from a voice message), metadata of themessage (such as a message header or metatag), the composition state ofthe message (e.g., whether the message currently is being composed orhas already been composed), the manifestation state of the message(e.g., whether the message currently is being manifested), thetransmission state of the message (e.g., whether the message currentlyis queued for transmission, attempted to be transmitted, or beingtransmitted), and the transmission direction of the message (e.g.,whether the message currently is being sent or received by the user,device, or application represented by output 208 b, 208 c, or 208 d,respectively). The message sensor 206 e may obtain input 214 e from anysource, such as an operating system of the device represented by devicesensor output 208 c or by using application program interface (API)calls to individual applications.

Sensor 206 f is a location sensor, which receives location input 214 fand, based on input 214 f, generates output 208 f representinginformation relating to a current location of either or both of the userrepresented by user output 208 b and the device represented by deviceoutput 208 c. The location sensor 206 f may obtain input 214 f from anysource, such as a Global Positioning System (GPS) device, a radiofrequency identification (RFID) tag, or manual user input. The locationsensor output 208 f may represent the current location in any of avariety of forms, such as a latitude-longitude combination, or by one ormore labels representing one or more categories of location (e.g., work,home, theater, restaurant). The location sensor 206 f may, alternativelyor additionally, obtain input 214 f relating to and provide output 208 frepresenting the proximity of the user and/or device to another userand/or device. Proximity data may, for example, be received directlyfrom another device using infrared (IR) signals, or by comparinglocations of user or devices to each other. Proximity output 208 f mayrepresent, for example, any one or more of the following: the degree ofproximity (e.g., distance) to another device, the identity of theproximate device, and whether the device represented by device output208 c is proximate to another device of interest.

Sensor 206 g is a velocity sensor, which generates output 208 grepresenting information relating to a current velocity of either orboth of the user represented by user output 208 b and the devicerepresented by device output 208 c. The velocity sensor 207 g may obtaindata from any source, such as any of the sources from which the locationsensor 206 f may obtain data. The velocity sensor 206 g may,alternatively or additionally, obtain data relating to and provideoutput 208 g representing the current acceleration of the current userand/or the current device.

Sensor 206 h is an activity sensor, which receives activity input 206 hand, based on input 206 h, generates output 208 h representinginformation relating to a current activity in which the current userand/or the current device is engaged. Examples of activities are writinga message, reading a message, writing a document, reading a document,engaging in a voice call, listening to a voice message, and providinginput of any kind to the current device. The activity sensor 206 h mayobtain input 214 h from any source, such as from any user input device(e.g., keyboard, mouse, touchpad, touchscreen, or microphone) or bymaking API calls to software such as operating systems, applicationprograms, and device drivers.

Sensor 206 i is a calendar sensor, which receives calendar input 214 iand, based on input 214 i, generates output 208 i representinginformation relating to data stored in a calendar of the current userand/or a calendar of the current device. Calendar output 208 i mayrepresent, for example, the presence or absence of an appointment at ornear the current time, and any information relating to any appointmentat or near the current time, such as the appointment's start time, endtime, duration, location, priority (e.g., high or low), category, andattendee list. The calendar sensor 206 i may obtain calendar input 214 ifrom any source, such as a calendar application external to the system200 (e.g., Microsoft Outlook, Apple iCal, Google calendar) or a calendarinternal to the system 200. Calendar input 214 i may, therefore,represent calendar appointments created in response to manual userinput.

Because information about calendar appointments in the future (e.g.,outside of the current sample period) may be useful, the calendar sensor206 i is not limited to generating output 208 i representing calendarappointments within the current sample period. Rather, for example, thecalendar sensor 206 i may receive input 214 i and generate output 208 irepresenting any number of calendar appointments at any time in the pastor future, such as calendar appointments occurring during the currentcalendar hour, day, week, or month; calendar appointments overlappingwith a period including the current sample period and extending for someamount of time into the future (e.g., one minute, ten minutes, 30minutes, one hour, or four hours); or the next appointment on thecalendar (i.e., the first appointment to appear on the calendar afterthe current sample period, but not including any appointment thatoverlaps with the current sample period).

Sensor 206 j is a user input sensor, which receives user input 214 jand, based on input 214 j, generates output 208 j representing inputprovided by a user, such as the current user, or any of the users 122a-b of the system. User input sensor 206 j may obtain data directly orindirectly from any user input device (e.g., keyboard, mouse, touchpad,touchscreen, or microphone) in response to the user providing input tosuch a device.

The particular context sensors 206 a-j shown in FIG. 2 are merelyexamples and not limitations of the present invention. Embodiments ofthe present invention may use fewer than all of the context sensors 206a-j, sensors other than the sensors 206 a-j shown in FIG. 2, or anycombination thereof.

In general, any of the profiles 110, 112 a-b, and 114 a-c of the system100 of FIG. 1 may be controlled by a corresponding profile controller.For example, referring to the system of FIG. 1F and the method 300 a ofFIG. 3A, a profile controller 140 may receive a request 142 from arequester 144 to read data from a profile 146 controlled by the profilecontroller 140 (operation 302), in response to which the profilecontroller 140 may read the requested data 148 from the correspondingprofile 146 (operation 304) and provide the requested data 148 (oroutput based on the requested data) to the requester 144 (operation306). The request 142 may, for example, be a request to read all of thedata in the profile 146 or a request to read a specified portion of theprofile 146, such as the values of one or more specified parameters inthe profile 146.

Similarly, referring to the system of FIG. 1G and the method 300 b ofFIG. 3B, the profile controller 140 may receive a request 152 from therequester to write data specified by the request 152 to thecorresponding profile 146 (operation 312), in response to which theprofile controller 140 may write the requested data to the correspondingprofile 146 (operation 314), thereby modifying the profile 146 asrequested by the request 152. The request 152 may, for example, be arequest to write data to the entire profile 146 or a request to writedata to a specified portion of the profile 146, such as a request towrite a specified value to a specified parameter of the profile 146.

In the case of FIGS. 1F and 1G, the requester may, for example, be ahuman user, a computer program, or a hardware component. Although onlythe generic profile controller 140 is shown in FIGS. 1F and 1G, itshould be understood that controllers specific to the system profile110, user profiles 112 a-b, and device profiles 114 a-c of FIG. 1A maybe implemented in accordance with the techniques disclosed in connectionwith FIGS. 1F and 1G.

Modifying (e.g., writing a value to) a profile may cause changes to bemade outside of the profile. For example, a device profile may include aparameter whose current value represents a current state of a feature ofthe device associated with the device profile. If the profile controller140 changes the value of such a parameter, the profile controller 140may also make a corresponding change to the state of the feature of theassociated device, or cause such a change to be made. For example, adevice profile associated with a telephone may include a “ring volume”parameter whose current value represents the current ring volume of thetelephone. If the profile controller 140 changes the value of the “ringvolume” parameter (such as by increasing the value to a higher value),the profile controller 140 may also make a corresponding change (e.g.,increase) to the device's ring volume, or cause such a change to bemade. For example, the device may include a mechanism that respondsautomatically to any change in the device's profile by making anappropriate corresponding change to a state of a feature of the device.

In general, any of the logic modules 102 a-c of the system 100 of FIG. 1may be controlled by a corresponding logic module controller. Forexample, referring to the system of FIG. 1 h and the method 300C of FIG.3C, a logic module controller 160 may receive a request 162 from arequester 164 to read data from a logic module 166 controlled by thelogic module controller 160 (operation 322), in response to which thelogic module controller 160 may read the requested data 168 from thecorresponding logic module 166 (operation 324) and provide the requesteddata 168 (or output based on the requested data) to the requester 164(operation 336). The request 164 may, for example, be a request to readone or more of the condition specifiers in the logic module 166 and/or arequest to read one or more of the action specifiers in the logic module166. The output data 168, therefore, may represent one or more of thecondition specifiers in the logic module 166 and/or a request to readone or more of the action specifiers in the logic module 166.

Similarly, referring to the system of FIG. 1I and the method 300 d ofFIG. 3D, the logic module controller 160 may receive a request 172 fromthe requester 164 to write data specified by the request 172 to thecorresponding logic module 166 (operation 332), in response to which thelogic module controller 160 may write the requested data to thecorresponding logic module 166 (operation 334), thereby modifying thelogic module 166 as requested by the request 172. The request 172 may,for example, be a request to modify/delete/add a condition specifierand/or to modify/delete/add an action specifier in the logic module 166.

In the case of FIGS. 1H and 1I, the requester 164 may, for example, be ahuman user, a computer program, or a hardware component. For example,the read request 162 and/or write request 172 may be input generated inresponse to the manual action of a human user.

Logic modules 102 a-c may be applied to the context data 202 to performthe actions 106 a-c specified by the logic modules 102 a-c if thecontext data 202 satisfies the conditions 104 a-c specified by the logicmodules 102 a-c. For example, referring to the system of FIG. 1J and themethod 300 e of FIG. 3E, a logic module execution unit 180 may beassociated with logic module 102 a. Although not shown in FIG. 1J,similar logic module execution units may be associated with logicmodules 102 b-c.

Logic module execution unit 180 receives some or all of context data 202as input (operation 352). Logic module execution unit 180 may, forexample, receive: (1) only a single one of the records 210 a-n withincontext data 202 as input, such as most recently-generated record, orthe record whose time field 212 a represents a time that is closest tothe current real time; (2) only a subset of the records 210 a-nassociated with a particular one of the users 122 a-b; or (3) only asubset of the records 210 a-n associated with a particular one of thedevices 124 a-c.

Logic module execution unit 180 determines whether the received contextdata 202 satisfies the condition specified by condition specifier 104 aof logic module 102 a (operation 354). If the logic module executionunit 180 determines that the received context data 202 satisfies thecondition, then, in response to the determination, the logic moduleexecution unit 180 performs the action specified by action specifier 106a of logic module 102 a, or causes the action to be performed (operation356). As mentioned above, action specifier 106 a may specify an actiontype or otherwise specify an action in generic terms, in which caseoperation 356 may include: (1) identifying (e.g., based on the receivedcontext data 202) one or more acts; and (2) performing the identifiedact(s) to implement the action specified by action specifier 106 a. As aresult, performing operation 356 multiple times for the same actionspecifier 106 a may cause the logic module execution unit 180 to performdifferent acts each time, based on differences in the context data 202received each time.

If the logic module execution unit 180 does not determine that thereceived context data 202 satisfies the condition specified by conditionspecifier 104 a, then the logic module execution unit 180 does notperform the action specified by action specifier 106 a of logic module102 a (operation 358). The method 300 e of FIG. 3E is an example of“applying” a logic module to context data, as the term “applying” isused herein.

The action 184 performed in response to the determination that thecontext 202 satisfies the condition specified by the logic module 102 amay be an action that modifies a profile (e.g., a system profile, a userprofile, or a device profile) or an action that modifies a logic module(e.g., a condition specifier or an action specifier of a logic module).For example, the logic module execution unit 180 may be the requester144 in FIGS. 1F and 1G, and the action 184 may be the read request 142(FIG. 1F) or the write request 152 (FIG. 1G). Similarly, the logicmodule execution unit 180 may be the requester 164 in FIGS. 1H and 1I,and the action 184 may be the read request 162 (FIG. 1H) or the writerequest 172 (FIG. 1I). As a result, changes in the context data 202 mayautomatically trigger changes in profiles and in logic modules.

As described above, a profile may be associated with one or more logicmodules. A profile may be “applied” (executed) by applying (executing)some or all of the logic modules associated with the profile. Forexample, referring to FIG. 1K, a profile execution unit 190 is shown.The profile execution unit 190 may execute (apply) a profile 192 (whichmay, for example, be any of the profiles shown in FIG. 1) by performingthe method 300 f of FIG. 3F in response to receipt of a trigger input196. The trigger input 196 may be any input, such as any of the sensorinputs 214 a-j, any of the context data 202, or manual user inputprovided using any input device. For example, if the trigger input 196is time sensor input 206 a, time sensor output 208 b, or time field 212a, the profile execution unit 190 may perform method 300 f periodicallyor according to a schedule.

The method 300 f identifies the profile 192 (operation 392) in any of avariety of ways. For example, if the system 100 includes only a singleprofile, then operation 362 may select the single profile. As anotherexample, operation 362 may select a profile based on user input. Asanother example, the method 300 f may loop over a plurality of profiles(e.g., all profiles in the system 100, all profiles associated with auser, or all profiles associated with a device), and select a particularone of such profiles in operation 362.

The method 300 f enters a loop over all logic modules 194 a-c associatedwith profile 192 (operation 364). Such logic modules 194 a-c may beidentified, for example, using associations of the kind shown in FIG.1E. For each such logic module (three of which are shown in FIG. 1Ksolely for purposes of example), the method 300 f applies the logicmodule to the context data 202 in any of the manners disclosed above inconnection with FIGS. 1J and 3E (operation 366). The method 300 frepeats operation 366 for any remaining logic modules associated withthe current profile (operation 368). The method 300 f repeats operations364-368 for any remaining profiles (operation 370).

Optionally, the system 100 may include two types of logic modules:action logic modules and trigger logic modules. An action logic moduleoperates in the manner disclosed above, such as in connection with FIGS.3E and 3F. A trigger logic module, like an action logic module, mayspecify a condition and an action, but additionally define a trigger.For example, referring again to FIG. 1A, logic modules 102 a-c are shownwith optional logic module types 108 a-c, respectively. Logic moduletype 108 a indicates whether logic module 102 a is an action or triggerlogic module; logic module type 108 b indicates whether logic module 102b is an action or trigger logic module; and logic module type 108 cindicates whether logic module 102 c is an action or trigger logicmodule.

The purpose of these two logic module types may be understood byreference to their operation. Referring to FIG. 3G, a flowchart is shownof a method 300 g for applying (executing) both types of profiles in thesystem 100. The method 300 g selects a profile (operation 382) in any ofthe manners described above in connection with operation 362 of method300 f of FIG. 3F.

The method 300 g enters a loop over any and all trigger logic modulesassociated with the current profile. Such logic modules may beidentified, for example, using associations of the kind shown in FIG. 1Eand by reference to the logic module type fields 108 a-c of the logicmodules 102 a-c. In other words, the loop initiated at operation 384 isnot a loop over all logic modules associated with the current profile,but only a loop over the trigger logic modules associated with thecurrent profile. For each such trigger logic module, the method 300 gdetermines whether the condition defined by the trigger logic module issatisfied by the context data 202, in any of the manners described abovein connection with operation 354 of method 300 e of FIG. 3E (operation386). If the context data 202 satisfies the condition of the currenttrigger logic module, then the method 300 g applies all action logicmodules associated with the current profile, in any of the mannersdisclosed above in connection with FIGS. 1J and 3E (operation 388).Otherwise, the method 300 g does not apply the action logic modulesassociated with the current profile to the context data 202. The method300 g repeats the operations described above for any remaining triggerlogic modules associated with the current profile (operation 390).

As the description above makes clear, the use of trigger logic modulesmay eliminate the need to apply (execute) action logic modules that donot, or are not likely to, satisfy the context data 202. As a result,the use of trigger logic modules may enable embodiments of the presentinvention to be implemented more efficiently than embodiments whichrequire that all logic modules associated with a profile be applied tothe context data 202.

For example, as will be described in more detail below, a profile may beassociated with a trigger logic module that defines a condition that issatisfied only when a message is detected, or only when a messagetransmissible via a particular communication mode is transmitted. Thesame profile may be associated with one or more action logic modulesthat define conditions that may be satisfied by particular features ofmessages transmissible via the particular communication mode. Use of atrigger logic module eliminates the need to apply the action logicmodules in circumstances in which their conditions are not satisfied.

The various components shown in FIGS. 1A-1K and FIG. 2, and the variousmethods shown in FIGS. 3A-3G, may be implemented in various physicalsystems. For example, such components and methods may be integrated intoa single device or distributed across multiple devices in any of avariety of ways. For example, FIG. 4A shows a system 400 a in whichvarious functions disclosed herein are implemented in a single device402, such as a desktop computer, handheld computer, cell phone, or othercomputing device or communication device.

For example, referring to FIG. 4A, a diagram is shown of one example ofa system 400 a that implements various features disclosed above. Thesystem 400 a includes a device 402, which includes a single deviceprofile 404. The device 402 also includes three logic modules 404 a-cwhich are associated 406 a-c with device profile 404. The device 402includes a single logic module controller 408 for controlling the logicmodules 404 a-c, and a single logic module execution unit 410 forexecuting all of the logic modules 404 a-c. The device 402 includes aprofile controller 412 for controlling the device profile 404, and aprofile execution unit 414 for executing the device profile 404. Thedevice 402 includes context data 416 and a context controller 418 forcontrolling the context data 416.

The elements of the device 402 may operate in the manner previouslydescribed. For example, profile controller 412 may read data from andwrite data to the device profile 404 in response to requests 420, theprofile execution unit 414 may execute the device profile 404 inresponse to a trigger 422, logic module controller 408 may read datafrom and write data to logic modules 404 a-c in response to requests424, logic module execution unit 410 may execute the logic modules 404a-c based on the context data 416, and context controller 418 may readfrom and write to the context data 416 based on sensor inputs 426.

Although device 402 may receive inputs (e.g., request 420, trigger 422,request 424, and sensor inputs 426) from any source, one such source isa human user who provides one or more such inputs manually using any oneor more input devices within and/or connected to the device 402. Any ofsuch inputs may, for example, be generated in response to and based onone or more gestures by the human user, such as a single gesture (e.g.,a single mouse click, a single keypress, a single touch, or a singlespoken word). The same is true of any inputs disclosed herein inconnection with any device.

As another example, referring to FIG. 4B, a diagram is shown of oneexample of another system 400 b that implements various featuresdisclosed above. The system 400 a includes two devices 432 a and 432 b,each of which may contain the same or similar components as the device402 of FIG. 4A. Therefore, for ease of illustration, various componentsfrom FIG. 4A are not shown within the devices 432 a-b of FIG. 4B.Instead, FIG. 4B illustrates that device 432 a includes a first deviceprofile 434 a and device 432 b includes a second device profile 434 bthat differs from the first device profile 432 a. The first deviceprofile 434 a may, for example, be associated with a first set of logicmodules (not shown), while the second device profile 434 b may, forexample, be associated with a second set of logic modules (not shown)that differs from the first set of logic modules. As a result, even ifthe two devices 432 a-b are provided with the same context data 416 asinput, the two devices 432 a-b may take different actions in response tosuch context data 416 due to differences in their device profiles 434a-b. Alternatively, for example, the devices 432 a-b may containidentical device profiles, or no device profiles, but contain userprofiles that differ from each other, thereby causing the devices 432a-b to take different actions in response to the same context data 416.

As another example, referring to FIG. 4C, a diagram is shown of oneexample of a system 400 c that implements various features disclosedabove. The system 400 c includes a profile server 442, which may be anykind of computing device, and which includes a user profile 444associated with a human user (not shown). The system 400 c also includesdevices 446 a and 446 b, each of which may contain the same or similarcomponents as the device 402 of FIG. 4A. Device 446 a includes userprofile 444′, which is identical in content to user profile 444 on theserver 442. Similarly, device 446 b includes user profile 444″, which isidentical in content to user profile 444 on server 442. If amodification is made to the user profile 444 at the server 442, theserver 444 may, in response, automatically transmit signals over anetwork 448 (such as the Internet) to both device 446 a and device 446 bsufficient to cause the modification to be reflected in user profiles444′ and 444″. Similarly, if a modification is made to the user profile444′ at the device 446 a, the device 446 a may, in response,automatically transmit signals over network 448 to server sufficient tocause the modification to be reflected in user profile 444; in responseto which the server 442 may automatically transmit signals over network448 to device 446 b sufficient to cause the modification to be reflectedin user profile 444″. The system 400 c may take similar action inresponse to a modification made to user profile 444″.

Similar techniques may be applied to system profiles and device profilesthat are replicated across multiple devices. Similar techniques may alsobe applied to profiles of any kind that are distributed across multipledevices, i.e., in which a first portion of one profile is stored on andapplied by a first device and in which a second portion of the sameprofile is stored on and applied by a second device.

As these examples illustrate, a “device” profile may, but need not, bestored on the device associated with the profile. For example, thedevice profile associated with a device may be stored solely on aserver, which contains a device profile controller that controls thedevice profile and uses the output of the device profile to control thedevice accordingly. As another example, the server may contain thedevice profile, while the device may contain the device profilecontroller, which may access the device profile remotely at the server.

Various execution modules, such as the profile controller 412, profileexecution unit 414, context controller 418, logic module controller 408,and logic module execution unit 410, may also be replicated acrossmultiple devices (including, e.g., clients and/or servers) and/ordistributed across multiple devices. In particular, any particularexecution module may execute on one device but process data located onanother device. For example, in the system 400 c of FIG. 4C, the profileserver 442 may contain a user profile controller (not shown) thatcontrols both the user profile 444 and the user profiles 444′ and 444″,in which case the devices 446 a and 446 b may not include user profilecontrollers. Similarly, any particular execution module may execute onone device and provide output to another device.

One or more of the associations disclosed herein, such as theassociations 136 a-g shown in FIG. 1E, may be implemented in recordstangibly stored on one or more non-transitory computer-readable media.For example, in FIG. 4A, associations 406 a-c between device profile 404and logic modules 404 a-c may be stored on one or more computer-readablemedia within the device 402. Associations may be replicated and/ordistributed across devices. Associations between two components may beimplemented by storing one element within the other. For example, anassociation between a logic module and a profile may be implemented bystoring the logic module (or a copy thereof) within the profile.

Any profile or logic module may have an activation state. An activationstate has is a parameter that has two permissible value: active andinactive. For ease of explanation, an activation state whose value isactive is referred to herein as an active activation state, while anactivation state who value is inactive is referred to herein as aninactive activation state. Similarly, a component (profile or logicmodule) whose activation state is active is referred to herein as anactive component, while a component whose activation state is inactiveis referred to herein as an inactive component. If a component isactive, then the component's controller applies (executes) the componentin any of the ways disclosed herein. If a component is inactive, thenthe component's controller may either not apply (execute) the component,or may apply the component but not generate any output from thecomponent. For example, if a logic module is inactive, then the logicmodule's controller may either not execute the logic module even if thecontext data satisfies the logic module's condition, or the logicmodule's controller may execute the logic module but not perform theaction specified by the logic module even if the context data satisfiesthe logic module's condition.

An activation state may, for example, be implemented as a special kindof logic module condition that takes precedence over any otherconditions specified by the logic module. In other words, the logicmodule's execution unit may, as part of determining whether the contextdata satisfies the logic module's conditions, treat the logic module'sactivation state as if it were part of the context data and determinewhether the logic module's activation state is active before determiningwhether any of the logic module's other conditions (if any) aresatisfied by the context data. As a result, if the logic module'sactivation state is inactive, the logic module's execution unit will notattempt to determine whether any of the logic module's other conditionsare satisfied by the context data, even if one or more other conditionsare satisfied by the context data.

The values of the activation states of distinct components may differfrom each other. As with any other data disclosed herein, the activationstate of a component may be tangibly stored in a non-transitorycomputer-readable medium, whether within the component itself orelsewhere. A component's controller may be used to read the value of acomponent's activation state and to write a value to (e.g., modify thevalue of) the component's activation state in any of the ways disclosedherein. For example, a component's controller may change a component'sactivation state from active to inactive or from inactive to active inresponse to manual user input, such as manual user input specifying thedesired activation state value, or manual user input indicating that theactivation state value should be toggled.

If multiple profiles are associated with a system, device, or user, anyone or more of such profiles may be active simultaneously. It may beuseful, however, for only one profile associated with a system, device,or user to be active at any particular time. In such a case, the profilethat is active is referred to herein as “the active profile” or “thecurrent profile” in connection with the system, device, or user.Embodiments of the present invention may enforce such a scheme bydetermining that a particular profile associated with a system, device,or user has become active and, in response to the determination,deactivating all of the other profiles associated with the system,device, or user. As described below, a profile associated with a system,device, or user may become the active profile in response to any of avariety of inputs, such as manual user input selecting the profile asthe active profile.

Certain embodiments of the present invention may be used in connectionwith the transmission of messages. For example, the conditions specifiedby logic modules may be satisfied by the detection of messages, byparticular message content, or by the identities of message sendersand/or recipients. As another example, the actions specified by logicmodules may be actions performed on messages, such as blocking,allowing, forwarding, or deferring messages.

For example, FIG. 5A shows an embodiment of a system 500 a which mayinclude any of the elements disclosed above (e.g., in FIGS. 1A-1K andFIG. 2), but which only shows elements of interest for ease ofillustration. The system 500 a includes a first logic module 502 a and asecond logic module 502 b. The first logic module 502 a includes one ormore condition specifiers 504 a and an action specifier 510 a. Morespecifically, the first logic module 502 a includes a firstcommunication mode condition specifier 506 a that specifies a conditionthat is satisfied by messages transmissible via a first communicationmode, and the second logic module 502 b includes a second communicationmode condition specifier 506 b that specifies a condition that issatisfied by messages transmissible via a second communication mode thatdiffers from the first communication mode.

The first logic module 504 a may, but need not, include one or moreadditional condition specifiers 508 a that may specify any of theconditions disclosed herein. Similarly, the second logic module 504 bmay, but need not, include one or more additional condition specifiers508 b that may specify any of the conditions disclosed herein. Althougheither or both of the additional conditions 508 a-b in FIG. 5A mayinclude an activation state, FIG. 5B explicitly shows an example of asystem 500 b in which logic modules 502 a-b contain activation states512 a-b.

The system 500 a may, but need not, also include any number ofadditional similar logic modules, such as a third logic module 502 cthat includes one or more condition specifiers 504 c and a third actionspecifier 510 c. The third condition specifiers 504 c may include athird communication mode condition specifier 506 c that specifies acondition that is satisfied by messages transmissible via a thirdcommunication mode that differs from both the first communication modeand the second communication mode. The third logic module 504 c may, butneed not, include one or more additional condition specifiers 508 c thatmay specify any of the conditions disclosed herein (including anactivation state, such as the activation state 512 c shown in FIG. 5C).

Each of the first, second, and third action specifiers 510 a-c mayspecify any action. The action specified by the first action specifier510 b may differ from the action specified by the second actionspecifier 510 b and from the action specified by the third actionspecifier 510 c. For example, no two of the actions specified by actionspecifiers 510 a-c may be the same as each other.

FIG. 5C shows an example of a system 500 c in which a device profile 520associated with logic modules 502 a-c includes an activation state 522,but in which the logic modules 502 a-c do not include activation states.As a result, when the device profile 520 is active, applying the deviceprofile 520 necessarily includes applying the logic modules 502 a-c;when the device profile 520 is inactive, applying the device profile 520does not include applying the logic modules 502 a-c.

FIG. 5D shows an example of a system 500 d in which a device profile 520associated with logic modules 502 a-c includes an activation state 522(as in FIG. 5C), and in which the logic modules 502 a-c includeactivation states 512 a-c (as in FIG. 5B). As a result, when the deviceprofile 520 is active, applying the device profile 520 includes applyingonly the active logic module(s) (if any) among logic modules 502 a-c;when the device profile 520 is inactive, applying the device profile 520does not include applying any of the logic modules 502 a-c, even activelogic modules. In other words, in the embodiment of FIG. 5D, theactivation state 522 of device profile 520 overrides the activationstates 512 a-c of logic modules 502 a-c.

Communications modes and examples thereof will be described in moredetail below. Examples, however, of first and second communicationmodes, or of first, second, and third communication modes that may bespecified by the communication mode condition specifiers disclosed abovein connection with FIG. 5A are: (1) email and voice calls; (2) email andtext messages; (3) voice calls and text messages; and (4) email, textmessages, and voice calls.

The system 500 a of FIG. 5A may, for example, be used to enable controlof messages transmissible via multiple distinct communication modes. Forexample, as shown in FIGS. 5C and 5D, device profile 520 may beassociated with two or more of the logic modules 502 a-c. The techniquesdisclosed herein may then be used to apply the associated logic modulesto messages transmissible via the device associated with the deviceprofile, and thereby to control messages transmissible via multiplecommunication modes in accordance with the logic modules associated withthe device profile. The same techniques may be applied if a systemprofile or a user profile, rather than a device profile, is associatedwith two or more of the logic modules 502 a-c.

For example, FIG. 6A shows a flowchart of a method 600 that may beperformed by the system 500 a of FIG. 5A. The system 500 a may detect afirst message transmissible via the first communication mode (operation602), in response to which the system 500 a may perform the first action(operation 604). The system 500 a may, for example, receive the firstmessage, determine whether the first message is transmissible via thefirst communication mode, and perform operation 604 only if the firstmessage is determined to be transmissible via the first communicationmode. The system 500 a may detect a second message transmissible via thesecond communication mode (operation 606), in response to which thesystem 500 b may perform the second action (operation 608).

FIG. 6B shows a flowchart of a method 610 that may be performed by thesystem 500 b of FIG. 5B. In the case of FIG. 5B, the system 500 b maydetect a first message transmissible via the first communication mode(operation 612). The system 500 b may determine whether the first logicmodule 502 a is active (operation 614). If the first logic module 502 ais active, the system 500 b may (in response to the determination)perform the first action (operation 616); otherwise, the system 500 bmay not perform the first action, even if the first message satisfiesall of the conditions 504 a of the first logic module 502 a. The system500 b may detect a second message transmissible via the secondcommunication mode (operation 618). The system 500 b may determinewhether the second logic module 502 b is active (operation 620). If thesecond logic module 502 b is active, the system 500 b may (in responseto the determination) perform the second action (operation 622);otherwise, the system 500 b may not perform the second action, even ifthe second message satisfies all of the conditions 504 b of the secondlogic module 502 a.

FIG. 6C shows a flowchart of a method 630 that may be performed by thesystem 500 c of FIG. 5C. The system 500 c may detect a first messagetransmissible via the first communication mode (operation 632). Thesystem 500 b may determine whether the device profile 520 is active(operation 634). If the device profile 520 is active, the system 500 cmay (in response to the determination) perform operation 604 asdescribed above; otherwise, the system 500 c may not perform operation604, even if the first message satisfies all of the conditions 504 a ofthe first logic module 502 a. The system 500 c may detect a secondmessage transmissible via the second communication mode (operation 636).The system 500 c may determine whether the device profile 520 is active(operation 638). If the device profile 520 is active, the system 500 cmay (in response to the determination) perform operation 608 asdescribed above; otherwise, the system 500 c may not perform operation608, even if the second message satisfies all of the conditions 504 b ofthe second logic module 502 a.

The method 630 of FIG. 6C need not make multiple determinations whetherthe device profile 520 is active (e.g., operations 634 and 638).Instead, for example, operations 634 and 638 may be removed from method630 and replaced with a single operation that is the same as operation634 or 638, but which is performed before operation 632, so thatoperations 602-608 are not performed if the device profile 520 isdetermined to be inactive, even if the system 500 c receives a messagetransmissible via the first communication mode or a messagetransmissible via the second communication mode. Similar techniques maybe applied to any system disclosed herein, to any kind of profile, andto logic modules having activation states.

As yet another example, if device profile 520 is inactive, then thesystem 500 c may not make any determination whether the device profile520 is active while the device profile 520 is inactive, even if thesystem 500 c receives a message transmissible via the firstcommunication mode or a message transmissible via the secondcommunication mode. An inactive device profile, in other words, mayeffectively be disabled so that the system 500 c does not apply thedevice profile (e.g., determine whether the device profile's conditionsare satisfied) while the device profile is inactive. Similar techniquesmay be applied to any system disclosed herein, to any kind of profile,and to logic modules having activation states.

FIG. 6D shows a flowchart of a method 650 that may be performed by thesystem 500 d of FIG. 5D. The system 500 d may detect a first messagetransmissible via the first communication mode (operation 652). Thesystem 500 d may determine whether the device profile 520 is active(operation 654). If the device profile 520 is active, the system 500 dproceed to operation 614 of FIG. 6B and perform the remainder of themethod 610 of FIG. 6B (operation 656). Otherwise, the system 500 d maynot perform operation 656 and may not otherwise apply the device profile520.

Changing activation states in the systems 500 b-d of FIGS. 5B-5D maycause the systems 500 b-d to change their handling of messages and othercontext. For example, consider the system 500 c of FIG. 5C. If thedevice profile 520 is active at a first time, then the system 500 c may,in response to receiving messages of the first and second communicationmodes, perform operations 602-604 and 606-608, as described above inconnection with FIG. 6C. Then, if the activation state 522 of the deviceprofile 520 is changed to inactive and the system 500 c receivesmessages of the first and second communication modes, the system 500 cmay not perform operations 602-604 or 606-608, as described above inconnection with FIG. 6C. The activation state 522 of the device profile520 may, as described above, be changed in response to user input. As aresult, a user may control whether the device profile 520 is active atany particular time and thereby control the manner in which the system500 c processes detected messages of various communication modes.

Condition specifiers, such as condition specifiers 508 a-c in FIG. 5,may, for example, specify conditions that are satisfied by context dataindicating that:

-   -   the current time is: a particular time of day, within a        particular time period (e.g., 9:00 AM-5:00 PM) on any day,        within a particular time period that satisfies an additional        condition (e.g., 9:00 AM-5:00 PM on a weekday), within a        particular day of the week, a particular day of any month (e.g.,        1^(st) or 15^(th)), on a holiday, within a user-specified time        period (e.g., a birthday or anniversary), or within a time        period delimited by a timer initiated at a previous time and        having either a specified duration or a specified end time;    -   the current user: is a particular user (e.g., having a        particular real name, user name, or other unique identifier        contained within a list or satisfying other conditions), has        particular privileges or access rights, or has provided        credentials satisfying predetermined criteria;    -   the current device: is a particular device (e.g., having a        particular serial number or unique identifier), is owned by or        otherwise associated with a particular user or class of user,        has or lacks particular communication capabilities (e.g., the        ability to transmit messages via a particular communication        mode), has or lacks hands-free capability (e.g., voice control),        has or lacks a particular kind of output device (e.g., a touch        screen or a text-to-speech reader), or has or lacks a particular        kind of input device (e.g., a microphone or touchscreen);    -   any application executing on the current device or associated        with the current user: is receiving input from a user (e.g.,        keyboard input or voice input), is providing output of any kind        to a user, is providing message-related output to a user (e.g.,        manifesting a message or a notification of a message), is        manifesting visual output, is manifesting auditory output, is        transmitting a message, or includes means for transmitting        messages (e.g., messages transmissible via one or more        predetermined communication modes);    -   a message: is being composed by the current user; is being        manifested to the current user; is being transmitted to or from        the current user or any device associated with the current user;        contains data (e.g., a body) satisfying predetermined criteria;        contains meta-data (e.g., subject, headers) satisfying        predetermined criteria; has a sender or recipient satisfying        predetermined criteria; has a priority satisfying predetermined        criteria; or has a time (e.g., time sent or time received)        satisfying predetermined criteria;    -   a current or scheduled location of a device: is a particular        location, is within a particular geographic area, is a        particular category of location (e.g., home, work, classroom,        restaurant, lecture hall, theater, vehicle, hospital), is an        exterior location, is an interior location;    -   a first device is in proximity to (e.g., within no more than        some predetermined maximum distance of) a second device, such as        any other device, or another device associated with a user        satisfying predetermined criteria (such as a user who is a        friend, family member, colleague, or within the same online        social network as the user associated with the first device);    -   a device is moving at a speed that is greater than or less than        a predetermined maximum or minimum speed, respectively;    -   a device's acceleration is greater than or less than a        predetermined maximum or minimum speed, respectively;    -   a current activity of a user: is a communicative activity (e.g.,        composing, sending, receiving, viewing, or reading a message),        is a particular category of activity (e.g., home, work, leisure,        study), includes providing any input to a device, or includes        providing input to a device using a particular kind of input        device (e.g., microphone, keyboard, or touchscreen);    -   a calendar indicates that: the current time is within an        appointment on the calendar, an appointment on the calendar is        scheduled to begin no more than some predetermined amount of        time later than the current time (e.g., 1 minute, 5 minutes, 30        minutes, 1 hour, 4 hours, or 1 day), an appointment on the        calendar was scheduled to begin no more than some predetermined        amount of time earlier than the current time (e.g., 1 minute, 5        minutes, 30 minutes, 1 hour, 4 hours, or 1 day), or an        appointment on the calendar was scheduled to end no more than        some predetermined amount of time earlier than the current time        (e.g., 1 minute, 5 minutes, 30 minutes, 1 hour, 4 hours, or 1        day);    -   user input indicates that: an activation state of a component        (e.g., profile or logic module) should be changed, a timer        should be started or stopped, a timer should have a specified        duration,

The items on the list above correspond to the context sensors 206 a-i,but omit the user input sensor 206 j because user input may contributeto or override any condition. For example, input received from a usermay override the time sensor 206 a by manually specifying a time otherthan the current time, in which case the context controller 204 maytreat the time specified by the user as the current time instead of thetime otherwise sensed by the time sensor 206 a. As another example, theuser may manually specify a location other than the user's actualcurrent location, in which case the context controller 204 may treat thelocation specified by the user as the current location instead of thelocation otherwise sensed by the location sensor 206 f.

As described above, any aspect of context data 202 may satisfy thecondition specified by a logic module. In the particular example of FIG.5, each logic module specifies at least one condition that is satisfiedby a message transmissible via a particular communication mode. Amessage that satisfies such a condition is referred to below as a“triggering message.” Action specifiers, such as action specifiers 510a-c in FIG. 5, may, for example, specify actions such as the following:

-   -   Block. Blocking a message may include any one or more of the        following: preventing the message from being sent, placed in an        output queue to be sent, provided to a software component        adapted to send messages, created, edited, manifested, received,        or downloaded. Blocking a message may include any one or more of        the following: preventing a notification of the message from        being generated, transmitted, or manifested.    -   Allow. Allowing a message may include, for example, not taking        any action in connection with the message. As a result,        associating an “allow” action type with a particular        communication mode may have the same effect as deactivating the        logic module whose condition is satisfied by messages        transmissible via the communication mode, and may be implemented        using the same techniques as deactivating the logic module whose        condition is satisfied by messages transmissible via the        communication mode. The effect of applying an “allow” action to        a particular message may be that the message is acted upon        (e.g., by a system external to the message control system 100)        in a manner that is the same as or equivalent to the manner in        which the message would have been acted upon if the message        control system 100 were not present.    -   Forward. Forwarding a message may, for example, include        transmitting the message to a new destination (e.g., user or        device) that differs from the original destination of the        message. The new destination may, for example, be explicitly        specified by the action specifier, or be derived from a rule        (e.g., “forward messages addressed to a recipient to that        recipient's administrative assistant”). Optionally, forwarding a        message may also include blocking the message. For example,        forwarding an email message originally transmitted to a first        user may include blocking the email message from being received        by the first user and transmitting the email message to a second        user.    -   Defer. Deferring a message may, for example, include blocking        the message until a timer elapses or until a predetermined        criterion is satisfied (e.g., until a predetermined time occurs)        and then allowing the message. Deferral, therefore, is        equivalent to and may be implemented using the same techniques        as blocking followed by allowing. The deferral period may, for        example, be explicitly specified by the action specifier or be        derived by a process from the current context (e.g., “on        weekdays, defer personal messages until 5 pm”).    -   Change mode. Changing the mode of a message may, for example,        include transmitting a message using a new mode that differs        from the original mode by which the message was transmitted. For        example, a message that was received at an email server using an        email protocol may be transmitted to the recipient user or        device using a text messaging protocol, either instead of or in        addition to transmitting the message to the recipient user or        device using an email messaging protocol. As this example        illustrates, changing the mode of a message may include blocking        the message. Changing the mode of a message may be implemented        using the same techniques as forwarding a message but with the        mode of the message changed.    -   Change contents. Changing the contents of a message may, for        example, include modifying the contents of the message to        produce a modified message and transmitting the modified        message, either instead of or in addition to the original        message. For example, an error message containing a numerical        error code may be modified to include an English-language        description that is easier for the recipient user to understand.        Changing the contents of a message may be implemented using        similar techniques to changing the mode of a message.    -   Respond. Responding to an original message may include sending a        response message to the original message, either via the same or        different communication mode from the original message.        Optionally, responding to an original message may include        blocking or deferring the original message. The contents of the        response may, for example, be specified explicitly by the action        specifier, or be derived by a process from the current context        (e.g., “I am in a scheduled meeting until 4:00 pm and cannot        respond to your email message until at least 4:15 pm”).

Any of the types of actions listed above may, for example, include: (1)performing the action on a particular triggering message in response todetection of the triggering message; or (2) initiating performance ofthe action on current and future messages (e.g., messages transmissiblevia the same communication mode as the triggering message, ortransmissible via communication modes that differ from the communicationmode of the triggering messages) until a future time (e.g., until theelapse of a timer, until a predetermined time occurs, or until someother condition is satisfied).

Although some of the examples of actions described herein are actionsthat are applied to messages, this is not a limitation of the presentinvention. An action may be applied to an object other than a message.Examples of actions include, but are not limited to:

-   -   launching, logging into, exiting, or logging out of one or more        applications, web sites, or accounts;    -   opening or closing files;    -   opening, displaying, closing, hiding, enabling, disabling,        changing the display order of (e.g., bringing to the front or        sending to the back), or changing the opacity, transparency,        color, or emphasis of any one or more GUI elements (e.g.,        windows, menus, dialog boxes, taskbars, or buttons);    -   changing the state of a device, such as by turning on, shutting        off, or changing the volume, brightness, contrast, or volume of        a device;    -   enabling or disabling input devices (such as keyboards, mice,        touchpads, touchscreens, microphones, or network adapters) or        output devices (such as monitors, screens, speakers, printers,        or network adapters).

An action specifier (such as any of the action specifiers 510 a-c) mayspecify not only an action to perform but also the object of the action(i.e., the object to which the action is to be applied). The actionspecifier may, for example, include an object specifier (not shown) thatspecifies the object of the action. The object specifier may specify theobject(s) of the action using a “condition” as that term is used herein,in which case the object(s) of the action may be selected as theobject(s) that satisfy the condition.

If an action specifier does not specify an object of the action, thenthe object of the action may be identified in other ways, such as byidentifying a default object or an object specified by another actionspecifier. For example, in various embodiments disclosed herein, theobject of an action may be identified as the message that satisfied thecondition that triggered the action and/or messages transmissible viathe same communication mode as the triggering message.

Certain actions may be particularly useful to perform in connection withparticular communication modes, such as:

-   -   Voice calls. For incoming calls: turning off the telephone        ringer, changing (e.g., lowering) the ringer volume, changing        the ring type (e.g., to vibrate or alarm), changing the ring        tone (e.g., from a musical tone to a beeping or ringing tone),        forwarding incoming calls directly to voicemail so that the        telephone does not ring, putting the caller on hold, and        disabling manifestation of notification of incoming voice calls.        For outgoing calls: preventing the user from initiating outgoing        calls (e.g., by disabling the dial pad, touchscreen, and/or        other input means on the telephone) and queuing outgoing calls        so that the user's speech is recorded and queued to be sent but        deferred until outgoing voice calls are activated, at which        point the outgoing call is automatically made and the user's        recorded speech is transmitted on the call.    -   Email messages. For incoming email messages: preventing        downloading of incoming email messages (or headers or other        indications of incoming email messages) from an email server to        an email client (optionally even if the user provides a manual        instruction to download email, and optionally even if the email        client is otherwise scheduled to download incoming email),        allowing downloading of incoming email messages from the email        server but preventing storing of the email messages in the        recipient's email inbox, allowing downloading of incoming email        messages from the email server and storing them in a folder        within the recipient's email inbox, allowing incoming email        messages to be added to the recipient's email inbox but        preventing manifestation of a notification of such messages,        preventing the user's inbox (or the bodies of messages contained        in the inbox) from being manifested, preventing the user from        issuing a command to receive email (such as by disabling a        “send/receive” button), and exiting from (i.e., terminating) one        or more email clients. For outgoing email, preventing new email        messages from being created, edited, sent, and/or queued to be        sent; in response to queuing of an outgoing email message to be        sent, deferring sending of the email message (e.g., until        blocking of sending email is deactivated); and exiting from        (e.g., terminating) one or more email clients.

The ability of modern computing and communication devices to multitask(i.e., to engage in multiple tasks simultaneously or apparentlysimultaneously) can be beneficial, but can also reduce the efficiency ofthe devices' users at achieving desired results. To address thisproblem, certain embodiments of the present invention enforce unitasking(the performance of only one task at a time) on devices that otherwiseare capable of multitasking.

For example, referring to FIG. 7A, a diagram is shown of a system 700including a plurality of devices 702 a-c. Such devices 702 a-c mayinclude any of the components disclosed herein, but are only illustratedto contain certain components for ease of illustration. In particular,device 702 a includes a communication mode module 704 a which is capableof transmitting messages via a first communication mode, a communicationmode module 706 a which is capable of transmitting messages via a secondcommunication mode, and a communication mode module 708 a which iscapable of transmitting messages via a third communication mode. No twoof the first, second, and third communication modes are the same as eachother.

Device 702 b includes a communication mode module 704 b which is capableof transmitting messages via the first communication mode and acommunication mode module 706 b which is capable of transmittingmessages via the second communication mode. Device 702 c includes acommunication mode module 708 c which is capable of transmittingmessages with the third communication mode. The first, second, and thirdcommunication modes may, for example, be email, text messaging, andvoice call communication modes.

The particular number and combination of devices, communication modes,and communication mode modules shown in FIG. 7A is merely an example andnot a limitation of the present invention. For example, the system 700may include fewer or greater than three communication devices (e.g., oneor two communication devices). Furthermore, the number of communicationmodes represented by the communication mode modules in the system 700 cmay be any number greater than or equal to two. The particulardistribution of communication mode modules among the devices 702 a-c isalso merely an example.

Each of communication mode modules 704 a-b, 706 a-b, 708 a, and 708 cmay, for example, be hardware, a computer program, or any combinationthereof. For example, an email communication mode module may include anycombination of one or more of the following: email client software, oneor more input devices for receiving email input (e.g., keyboard ortouchscreen), one or more output devices for providing email output(e.g., monitor, touchscreen, or speakers), and one or more networkcommunication devices (e.g., wired or wireless network card).

Multiple communication mode modules within a single device may becapable of executing in parallel with each other or substantially inparallel with each other (e.g., by utilizing multi-tasking capabilitiesof the device). For example, communication mode modules 704 a, 706 a,and 708 a may be capable of executing in parallel with each other ondevice 702 a, so that they can perform their communication mode-relatedfunctions in parallel with each other.

The system 700 also includes a system profile 710 that is associatedwith all of the devices 702 a-c. The system profile 710 includes atleast two logic modules; three such logic modules 712 a-c are shown inFIG. 7A for purposes of example. Although the logic modules 712 a-c mayspecify any conditions and any actions, a particular set of conditionsand actions will now be described that may be used to enforcecommunication mode unitasking on and/or across the devices 702 a-c. Theterm “communication mode unitasking” refers herein to engaging in (e.g.,composing, reading, or transmitting) communication of messagestransmissible via only one communication mode at any particular time.For example, the system 700 c may prevent users of the system 700 cfrom: (1) engaging in text messaging or voice call communication whileengaged in email communication; (2) engaging in email communication ortext messaging communication while engaged in voice call communication;and (3) engaging in voice call communication or email communicationwhile engaged in text messaging communication. The system 700 may allowthe user to switch from unitasking in connection with a firstcommunication mode to unitasking in connection with a secondcommunication mode; this is referred to here as “sequentialcommunication mode unitasking.”

Communication mode unitasking may, for example, be implemented byconfiguring any two or more of logic modules 712 a-c as follows: (1) theconditions 714 a of logic module 712 a are satisfied by detection of anemail message; (2) the action 716 a of logic module 712 a blocks textmessages and voice calls; (3) the conditions 714 b of logic module 712 bare satisfied by detection of a voice call; (4) the action 716 b oflogic module 712 b blocks email messages and text messages; (5) theconditions 714 c of logic module 712 c are satisfied by the detection ofa text message; and (6) the action 716 c of logic module 712 c blocksemail messages and voice calls.

An effect of implementing the system 700 is illustrated by the method800 of FIG. 8A, which may be performed by the system 700 by applying thetechniques disclosed herein. The method 800 determines whether any ofthe devices 702 a-c associated with the system profile 710 is engaged inemail communication (operation 802), such as by analyzing the contextdata 202 to detect whether any of the devices 702 a-c is composing,manifesting, or transmitting an email message. If any of the devices 702a-c is engaged in email communication, then the method 800 blocks textmessage communication and voice call communication on all of the devices702 a-c (operation 804).

The method 800 determines whether any of the devices 702 a-c associatedwith the system profile 710 is engaged in voice communication (operation806). If any of the devices 702 a-c is engaged in voice communication,then the method 800 blocks email communication and text messagecommunication on all of the devices 702 a-c (operation 808). Finally,the method 800 determines whether any of the devices 702 a-c associatedwith the system profile 710 is engaged in text message communication(operation 810). If any of the devices 702 a-c is engaged in textmessage communication, then the method 800 blocks email communicationand voice call communication on all of the devices 702 a-c (operation812).

The system 700 may block messages transmissible via a particularcommunication mode by, for example, performing any one or more of thefollowing in connection with the communication mode module(s) in thesystem 700 that are capable of transmitting messages via the particularcommunication mode (the “blocked communication mode modules”): (1)disabling or shutting down the blocked communication mode modules; (2)intercepting incoming messages addressed to the blocked communicationmode modules and preventing the intercepted messages from being providedto the blocked communication mode modules; (3) intercepting outgoingmessages attempted to be sent by the blocked communication mode modulesand preventing the intercepted messages from being provided to theirintended destinations; (4) preventing the blocked communication modemodules from being used to compose messages of the correspondingcommunication mode; and (5) preventing the blocked communication modemodules from manifesting messages of the corresponding communicationmode.

The blocking of a communication mode performed by FIG. 7A in method 800may, but need not, include blocking of all messages transmissible viathe communication mode, or blocking of all activities performed inconnection with messages transmissible via the communication mode. Forexample, such blocking may include only blocking of incoming messages,only blocking of outgoing messages, only blocking of composing ofmessages, or only blocking of manifesting messages.

The blocking of a communication mode performed by FIG. 7A in method 800may continue until manually discontinued in response to user input, oruntil the context data 202 satisfies some predetermined condition (suchas the lapse of a timer). For example, a user of the devices 702 a-c mayengage in communication of a first communication mode (e.g., email) andthereby cause the system 700 to block communications of the remainingcommunication modes (e.g., text message and voice calls). The system 700may block incoming communications of the blocked communication modesunless and until the user of the devices 702 a-c engages in activityrelated to one of the blocked communication modes, such as composing amessage transmissible by one of the blocked communication modes orviewing an inbox of messages transmissible by one of the blockedcommunication modes. The system 700 may detect such activity by the userand treat it as an input to method 800, i.e., as an indication that theuser now wants to unitask in the newly-engaged communication mode. Inresponse, the system 700 may allow messages transmissible via the newcommunication mode but block messages transmissible via the remainingcommunication modes. In this way, the user may engage in sequentialunitasking with a minimum of effort.

As another example, the system 700 may not allow the user to manuallydiscontinue unitasking in connection with a particular communicationmode. Instead, the system 700 may be configured only to discontinueunitasking entirely, or to discontinue unitasking in connection with onecommunication mode and initiate unitasking in connection with anothercommunication mode, in response to satisfaction of a predeterminedcondition by the context 202, where the predetermined condition is notbased on user input (or at least that the predetermined condition is notbased on user input provided by the user at or around the time at whichthe system 700 determines whether the predetermined condition issatisfied). In such an embodiment, the system 700 may or may not allowthe user to effectively discontinue unitasking by changing theactivation state of the system profile 710 and/or of other profiles inthe system 700.

As another example, the actions defined by logic modules 712 a-c may be“change mode” rather than block. As a result, in response to detectingthat the user is engaged in email communication, the system 700 mayperform a “change mode to email” action in connection with any messagestransmissible via other communication modes (e.g., text messaging andvoice calls) that the system 700 detects while the system 700 isunitasking in connection with email. Any incoming text messages receivedduring this time may, therefore, be converted into email messages anddelivered to the user's email inbox, and any incoming voice callsreceived during this time may, therefore be converted (using anautomated speech recognition engine) into email messages and deliveredto the user's email inbox (possibly in addition to storing a recordingof the voice call as a voicemail message in the user's voicemail inbox).Similarly, in response to detecting that the user is engaged in livevoice call communication, the system 700 may perform a “change mode tovoice call” action in connection with any messages transmissible viaother communication modes (e.g., text messaging and email) that thesystem 700 detects while the system 700 is unitasking in connection withlive voice calls. Any incoming text messages or email messages receivedduring this time may, therefore, be converted (using a text-to-speechengine) into live voice calls and/or voicemail messages that aredelivered to the user. Similar techniques may be applied when the useris unitasking in connection with text messages.

Communication mode unitasking is merely one example of “enforcedunitasking,” as that term is used herein. Embodiments of the presentinvention may engage in enforced unitasking by limiting a system (e.g.,a computing device or software) to performing only a subset of the setof tasks that the system inherently is capable of performing. The subsetmay include one, two, three, or any number of tasks fewer than the totalnumber of tasks that the system inherently is capable of performing.

For example, referring to FIG. 7B, a diagram is shown of a system 720including a plurality of computing devices 722 a-c. Such devices 722 a-cmay include any of the components disclosed herein, but are onlyillustrated to contain certain components for ease of illustration. Inparticular, device 722 a includes a first task module 724 a which iscapable of performing a first task, a second task module 726 a which iscapable of performing a second task, and a third task module 728 a whichis capable of performing a third task. No two of the first, second, andthird tasks are the same as each other.

Device 722 b includes a first task mode module 724 b which is capable ofperforming the first task and a second task mode module 726 b which iscapable of performing the second task. Device 722 c includes a thirdtask module 728 c which is capable of performing the third task.

The particular number and combination of devices and task modules shownin FIG. 7B is merely an example and not a limitation of the presentinvention. For example, the system 720 may include fewer or greater thanthree computing devices (e.g., one or two computing devices).Furthermore, the number of tasks represented by the task modules in thesystem 700 may be any number greater than or equal to two. Theparticular distribution of task modules among the devices 722 a-c isalso merely an example.

Each of task modules 724 a-b, 726 a-b, 728 a, and 728 c may, forexample, contain or otherwise be associated with one or more hardwarecomponents, one or more computer programs, or any combination thereof.In other words, a particular task module may contain or otherwise beassociated with any combination of hardware and/or software componentsfor performing the particular task associated with the task module. Acomponent of a task module need not be a standalone product. Rather, forexample, a component of a task module may be a component or subset of aproduct. For example, if task module 724 a is associated with the taskof transmitting email messages, then task module 724 a may include: (1)a computer program for transmitting email; and (2) an email clientcomponent of a web browser. Although task modules 724 a, 724 b, and 724c are associated with distinct tasks, the contents of task modules 724a, 724 b, and 724 c may overlap with each other. For example, if taskmodule 724 a is associated with the task of transmitting email messagesand task module 724 b is associated with the task of creatingappointments on a calendar, then task modules 724 a and 724 b maycontain (or otherwise be associated with) a computer program thatincludes both means for transmitting email messages and means forcreating calendar appointments.

Multiple task modules within a single device may be capable of executingin parallel with each other or substantially in parallel with each other(e.g., by utilizing multi-tasking capabilities of the device). Forexample, task modules 724 a, 726 a, and 728 a may be capable ofexecuting in parallel with each other on device 722 a, so that they canperform their respective tasks in parallel with each other.

The term “task,” as that term is used herein, may refer, for example, toany one or more of the following:

-   -   transmitting or attempting to transmit any message (e.g.,        sending a message and/or receiving a message), or transmitting        or attempting to transmit a message that satisfies a particular        condition;    -   manifesting or attempting to manifest a message or a        notification of a message;    -   creating a new message or attempting to create a new message;    -   editing an existing message or attempting to edit an existing        message;    -   using a particular device for any purpose, or using a device to        perform a task that satisfies a particular condition;    -   using a particular component (e.g., a particular input component        or a particular output component) of a device for any purpose,        or using a component of a device to perform a task that        satisfies a particular condition;    -   using a particular application for any purpose, or using a        particular application to perform a task that satisfies a        particular condition;    -   using a particular user interface element for any purpose, or        using a particular user interface element to perform a task that        satisfies a particular condition.

The system 720 also includes a system profile 730 that is associatedwith all of the devices 722 a-c. The system profile 730 includes atleast two logic modules; three such logic modules 732 a-c are shown inFIG. 7B for purposes of example. Although the logic modules 732 a-c mayspecify any conditions and any actions, a particular set of conditionsand actions will now be described that may be used to enforce unitaskingon and/or across the devices 722 a-c. In particular, the system 720 mayprevent users of the system 720 from: (1) performing the second andthird tasks (i.e., the tasks associated with task modules 726 a and 728b, respectively) while performing the first task (i.e., the taskassociated with task module 704 a); (2) performing the first and thirdtasks (i.e., the tasks associated with task modules 704 a and 708 a,respectively) while performing the second task (i.e., the taskassociated with task module 706 a); and (3) performing the first andsecond tasks (i.e., the tasks associated with task modules 704 a and 706a, respectively) while performing the third task (i.e., the taskassociated with task module 708 a). The system 720 may allow the user toswitch from unitasking in connection with one task to unitasking inconnection with another task; this is referred to here as “sequentialenforced unitasking.”

Sequential enforced unitasking may, for example, be implemented byconfiguring any two or more of logic modules 732 a-c as follows: (1) thecondition 734 a of logic module 732 a is satisfied by detecting that anyof the devices 722 a-c is performing the first task; (2) the action 736a of logic module 732 a prevents devices 702 a-c from performing eitheror both of the second and third tasks (such as by disabling and/orreconfiguring task modules 706 a, 708 a, 706 b, and 708 c); (3) thecondition 734 b of logic module 732 b is satisfied by detecting that anyof the devices 722 a-c is performing the second task; (4) the action 736b of logic module 732 b prevents devices 702 a-c from performing eitheror both of the first and third tasks (such as by disabling and/orreconfiguring task modules 704 a, 708 a, 704 b, and 708 c); (5) thecondition 734 c of logic module 732 c is satisfied by detecting that anyof the devices 722 a-c is performing the third task; and (6) the action736 c of logic module 732 c prevents devices 702 a-c from performingeither or both of the first and second tasks (such as by disablingand/or reconfiguring task modules 704 a, 706 a, 704 b, and 706 b).

An effect of implementing the system 720 is illustrated by the method820 of FIG. 8B, which may be performed by the system 720 by applying thetechniques disclosed herein. The method 820 determines whether any ofthe devices 722 a-c associated with the system profile 730 is performingthe first task (operation 822), such as by analyzing the context data202 to detect whether any of the devices 722 a-c is performing the firsttask. If any of the devices 722 a-c is performing the first task, thenthe method 820 prevents the devices 722 a-c from performing the secondor third tasks (operation 824).

The method 820 determines whether any of the devices 722 a-c associatedwith the system profile 730 is performing the second task (operation826), such as by analyzing the context data 202 to detect whether any ofthe devices 722 a-c is performing the second task. If any of the devices722 a-c is performing the second task, then the method 820 prevents thedevices 722 a-c from performing the first or third tasks (operation828).

The method 820 determines whether any of the devices 722 a-c associatedwith the system profile 730 is performing the third task (operation830), such as by analyzing the context data 202 to detect whether any ofthe devices 722 a-c is performing the third task. If any of the devices722 a-c is performing the third task, then the method 820 prevents thedevices 722 a-c from performing the first or second tasks (operation832).

Once the method 800 of FIG. 8B has begun to prevent one or more tasksfrom being performed, the method 800 may continue to prevent such tasksfrom being performed until such prevention is discontinued by the method800 in response to input provided manually by a user, or until thecontext data 202 satisfies some predetermined condition (such as thelapse of a timer, a change in location, or a change in speed).

As another example, the system 720 may not allow the user to manuallydiscontinue unitasking in connection with a particular task. Instead,the system 720 may be configured only to discontinue unitaskingentirely, or to discontinue unitasking in connection with one task andinitiate unitasking in connection with another task, in response tosatisfaction of a predetermined condition by the context 202, where thepredetermined condition is not based on user input (or at least that thepredetermined condition is not based on user input provided by the userat or around the time at which the system 720 determines whether thepredetermined condition is satisfied). In such an embodiment, the system720 may or may not allow the user to effectively discontinue unitaskingby changing the activation state of the system profile 730 and/or ofother profiles in the system 720.

In the embodiment illustrated by FIGS. 7B and 8B, detection of theperformance of a single task within a set of tasks causes theperformance of all other tasks in the set to be prevented. This ismerely one example and does not constitute a limitation of the presentinvention. Alternatively, for example, the detection of the performanceof any one or more tasks may cause any one or more other tasks to beprevented. For example, referring to FIG. 7C, a diagram is shown of aplurality of unitasking specifiers 740 a-c, each of which specifies oneor more tasks to be prevented in response to detection of theperformance of one or more other tasks.

More specifically, unitasking specifier 740 a includes a triggering tasklist 742 a, which specifies the task(s) that trigger the unitaskingspecifier 740 a, and a prevented task list 746 a, which specifies thetask(s) that are prevented from being performed when the unitaskingspecifier 740 a is triggered. In particular, the triggering task list742 a includes a single triggering task specifier 744 a, which mayspecify any task. Furthermore, the prevented task list 746 a includesthree prevented task specifiers 748 a-c, which may specify any threedistinct tasks. The method 820 of FIG. 8B may be generalized so thatoperation 822 determines whether any of the devices 722 a-c isperforming any of the tasks specified by the triggering task list 746 a,and so that operation 824 prevents the devices 722 a-c from performingany of the tasks specified by the prevented task list 746 a.

Unitasking specifier 740 b includes a triggering task list 742 b and aprevented task list 746 b. In particular, the triggering task list 742 bincludes a first triggering task specifier 754 a and a second triggeringtask specifier 754 b, which may specify any two distinct tasks.Furthermore, the prevented task list 746 b includes three prevented taskspecifiers 758 a-c, which may specify any three distinct tasks. Themethod 820 of FIG. 8B may be generalized so that operations 826 and 828apply to the triggering task list 742 b and the prevented task list 746b, respectively.

Finally, unitasking specifier 740 c includes a triggering task list 742c and a prevented task list 746 c. In particular, the triggering tasklist 742 c includes a first triggering task specifier 764 a and a secondtriggering task specifier 764 b, which may specify any two distincttasks. Furthermore, the prevented task list 746 b includes a singleprevented task specifier 768 a, which may specify any task. The method820 of FIG. 8B may be generalized so that operations 830 and 832 applyto the triggering task list 742 c and the prevented task list 746 c,respectively.

As the examples in FIG. 7C illustrate, there may be a one-to-one,one-to-many, many-to-one, or many-to-many relationship between the tasksin the triggering task list of a unitasking specifier and the tasks inthe prevented task list of that unitasking specifier. Furthermore, thetriggering task list and the prevented task list of a particularunitasking specifier may be disjoint; in other words, the triggeringtask list may contain no tasks that are in the prevented task list, andthe prevented task list may contain no tasks that are in the triggeringtask list.

Furthermore, the union of the triggering task list and the preventedtask list of a particular unitasking specifier may specify fewer thanall of the tasks that a particular one of the devices 722 a-c in thesystem 720 (or the set of devices 722 a-c in the system) is capable ofperforming. For example, the union of triggering task list 742 a andprevented task list 746 a may specify a set of tasks that does notinclude the task associated with task modules 728 a and 728 c in FIG.7B. As a result, when the system 720 applies the unitasking specifier740 to prevent the tasks specified by the prevented task list 746 a frombeing performed by the devices 722 a-c, such prevention may not includepreventing task modules 728 a and 728 c from performing their associatedtask. As a result, task modules 728 a and 728 c may continue to performtheir associated task even while the system 720 and method 820 preventtask modules 724 a, 726 a, 724 b, and 726 b from performing theirrespective tasks.

Unitasking-based features of embodiments disclosed herein may be used inconnection with any other embodiments disclosed herein. Unitasking-basedfeatures of embodiments disclosed herein may, however, be usedindependently of various features disclosed herein. For example,unitasking-based features of embodiments disclosed herein may be used inconnection with profiles or without the use of profiles.

Referring FIG. 9A, an example of a user interface 900 a representing aparticular profile (e.g., the system profile 710 in FIG. 7A) is shown.This and other users interfaces disclosed herein are merely examples andnot limitations of the present invention. The user interface 900 aincludes a first mode section 904 a representing a first logic module(e.g., logic module 712 a) having a first condition that is satisfied bya first communication mode; a second mode section 904 b representing asecond logic module (e.g., logic module 712 b) having a second conditionthat is satisfied by a second communication mode; and a third modesection 904 c representing a third logic module (e.g., logic module 712c) having a third condition that is satisfied by a third communicationmode. In the example of FIG. 9A, the three communication modes areemail, text messaging, and voice calls. In particular:

-   -   the first mode section 904 a includes: (1) a mode identification        element 906 a indicating the mode that satisfies the condition        specified by condition specifier 714 a; and (2) a manifestation        of the first mode action represented by the first mode action        specifier 716 a, namely an element 908 a in the form of a circle        containing the word “block”;    -   the second mode section 904 b includes: (1) a mode        identification element 906 b indicating the mode that satisfies        the condition specified by condition specifier 714 b; and (2) a        manifestation of the first mode action represented by the first        mode action specifier 716 b, namely an element 908 b in the form        of a circle containing the word “allow”; and    -   the third mode section 904 c includes: (1) a mode identification        element 906 c indicating the mode that satisfies the condition        specified by condition specifier 714 c; and (2) a manifestation        of the first mode action represented by the first mode action        specifier 716 c, namely an element 908 c in the form of a circle        containing the word “forward.”

The user interface 900 a, therefore, represents the contents of thecorresponding profile at a particular time. The user interface 900 a mayalso be used to receive user input for modifying the contents of thecorresponding profile. In other words, the user interface 900 a may be amechanism for receiving, from a user, input to provide to a profilecontroller and thereby to cause the profile controller to modify thecontents of the profile based on the input, as disclosed above inconnection with FIGS. 1G and 3B.

For example, the user may provide input through the user interface 900 ato modify the first condition specifier 714 a by:

-   -   editing the text of the first mode identification element 906 a        to specify a communication mode that differs from the        communication mode currently specified by the first mode        specifier 906 a (e.g., by editing the text “Email” to read        “Fax”);    -   selecting the first mode identification element 906 a, thereby        causing a drop-down list of available communication modes to be        displayed, and by then selecting an alternate communication mode        (e.g., “Fax”) from the list; or    -   selecting (e.g., clicking on) the first mode identification        element 906 a one or more times, thereby causing labels of        available communication modes (e.g., “Email,” “Text,” “Voice,”        “Fax”) to be manifested sequentially in response to each        selection, until a label of the communication mode desired by        the user is manifested.

Similarly, the user may, for example, provide input to the userinterface 900 a to modify the first action specifier 716 a by:

-   -   selecting the first mode action element 908 a, thereby causing a        drop-down list of available actions (e.g., “Block,” “Allow,”        “Forward,” and “Defer”) to be displayed, and then selecting an        alternate action (e.g., “Allow”) from the list; or    -   selecting (e.g., clicking on) the first mode action element 908        a one or more times, thereby causing labels of available actions        (e.g., “Allow,” “Forward,” “Defer,” and “Block”) to be        manifested sequentially in response to each selection, until a        label of the action desired by the user is manifested.

If individual logic modules in a profile have activation states (as inthe case of FIG. 5B), such a profile may be manifested by the userinterface 900 b of FIG. 9B. The user interface 900 b of FIG. 9B issimilar to the user interface 900 a of FIG. 9A, except that the userinterface 900 b of FIG. 9B includes first mode activation element 910 a,which manifests an activation state of its corresponding logic module;second mode activation element 910 b, which manifests an activationstate of its corresponding logic module; and third mode activationelement 910 c, which manifests an activation state of its correspondinglogic module. To modify the activation states of the first correspondinglogic module, the user may select (e.g., click on) first mode activationelement 910 a, in response to which the corresponding logic modulecontroller may toggle the value of the corresponding activation statespecifier from its current value (e.g., “active”) to its alternate value(e.g., “inactive”).

If a profile has an activation state (as in the case of FIG. 5C), such aprofile may be manifested by the user interface 900 c of FIG. 9C, whichis similar to the user interface 900 a of FIG. 9A, except that the userinterface 200 c of FIG. 9C further includes a profile activation element912, which manifests the activation state of the corresponding profile.To modify the activation state of the corresponding profile, the usermay select (e.g., click on) profile activation element 910 c, inresponse to which the corresponding profile controller may toggle thevalue of the corresponding activation state specifier from its currentvalue (e.g., “active”) to its alternate value (e.g., “inactive”).

If both a profile and its associated logic modules have activationstates (as in the case of FIG. 5D), such a profile and associated logicmodules may be manifested by the user interface 900 d of FIG. 9D, whichcombines elements of the user interfaces 900 b (FIG. 9B) and 900 c (FIG.9C).

As another example, distinct profiles may have names or other uniqueidentifiers, such as “work,” “home,” and “school,” or “weekday” and“weekend.” Embodiments of the present invention may provide userinterfaces that enable a user to select a particular profile and therebymake the selected profile the active profile by selecting the profile'sname, such as by selecting the name from a list or speaking the name ofthe profile. Such a user interface may also allow the user to select andactivate/deactivate a profile by issuing a single command, such as“activate work” or “deactivate home.” As yet another example, a userinterface may enable a user to either deactivate all profiles or selecta particular profile as the active profile by issuing a single command,e.g., by speaking a single word or phrase, or by selecting a single wordor phrase from a list, where an example of such a list is: “Disable,”“Home,” “Work,” and “Car.” In this example, selecting “Disable” causesall profiles (e.g., all profiles, or all system, device, or userprofiles) to be disabled, while selecting any one of “Home,” “Work,” and“Car” causes a corresponding profile to be selected as the activeprofile.

As another example, user interfaces may enable the user to select logicmodules and/or to configure logic modules without the use of profiles.For example, a user interface may enable a user to select a particularcombination of two or more logic profiles, such as by selecting suchprofiles from a list, where an example of such a list is: “Disable,”“Email: Block, Text: Allow, Voice: Forward,” “Email: Allow, Text: Allow:Voice: Block,” and “Email: Forward, Text: Forward, Voice: Forward.” Inthis example, selecting “Disable” causes all logic modules (e.g., alllogic modules associated with a system, device, or user) to be disabled,while selecting any other entry from the list causes a correspondingcombination of logic modules to be selected as the current logicmodules.

Any of the techniques disclosed herein may be implemented, for example,as: (1) standalone components (e.g., hardware and/or computer programs),which may or may not interoperate with existing components (e.g.,existing computing devices, existing messaging software); (2) plug-insto existing components; or (3) integral modifications to existingcomponents. Implementing plug-in embodiments may, for example, includeinstalling the plug-in to the existing component using a plug-ininterface provided by the existing component. Embodiments that are notimplemented as integral modifications to existing components may, forexample:

-   -   implement actions such as blocking messages by performing one or        more of the following: (1) intercepting messages (and other        input) addressed to such components and preventing such input        from reaching such components; (2) intercepting messages (and        other output) generated by such components and preventing such        output from reaching its designated destination; (3) disabling        or enabling such components, or sub-components thereof; and (4)        modifying the configurations of such components, such as by        using API calls; and    -   implement actions such as allowing messages by performing one or        more of the following: (1) intercepting messages (and other        input) addressed to such components and forwarding such input to        such components; (2) intercepting messages (and other output)        generated by such components and forward such output to its        designated destination; (3) enabling such components, or        sub-components thereof, and then not intercepting input        addressed to or output generated by such components; and (4)        modifying the configurations of such components, such as by        using API calls.

Embodiments of the present invention may respond in a variety of ways tochanges in the activation states of profiles and logic modules. Forexample, if a logic module is inactive and then becomes active, thetechniques disclosed herein may begin to apply the logic module to thecontext data 202. For example, if the condition specified by the logicmodule is satisfied by a particular class of messages, then thetechniques disclosed herein may begin to perform the action specified bythe logic module in response to detection of messages in the particularclass.

It may, however, be desirable to take additional actions, or to modifythe actions performed by the logic module, in anticipation of a futuretransition of the logic module from active to inactive. For example, ifthe action specified by the logic module is “block,” then it may bedesirable, upon a transition of the logic module from active toinactive, to “unblock” any messages that were blocked by the logicmodule while it was active. Such a result may be achieved by, forexample, implementing a “block” action as a “defer” action, where thecondition that terminates the “defer” action is the transition of thelogic module from active to inactive. The “defer” action may, forexample, store deferred messages in a deferral queue. Upon transition ofthe logic module from active to inactive, messages in the deferral queuemay, for example, be delivered to their designated destination. Forexample, incoming messages that were prevented from being inserted intoan inbox by the “defer” action may be inserted into the inbox upontransition of the logic module from active to inactive, and outgoingmessages that were prevented from being transmitted to theirdestinations may be transmitted to their destinations upon transition ofthe logic module from active to inactive. More generally, in response totransition of a logic module from active to inactive, any actions thatwere prevented from being performed by the logic module while the logicmodule was active may be performed.

The same techniques may be applied in connection with changes in theactivation state of a profile (e.g., a system, device, or user profile)that is associated with the logic module, assuming that the logic moduleis active. In other words, if a logic module is active, then thetransition of a profile associated with the logic module from inactiveto active may be implemented in the same way as a transition of thelogic module from inactive to active, and the transition of the profilefrom active to inactive may be implemented in the same way as atransition of the logic module from active to inactive.

As another example, when a logic module (or associated profile)transitions from inactive to active, the state of components (such asemail clients, instant messaging clients, web browsers, VoIP clients,desktop computers, laptop computers, smartphones, and tablet computers)that may be affected by the actions of the logic module may be stored.In particular, any state that is modified in response to a transition ofa logic module from inactive to active may be saved before that state ismodified. For example, when a logic module transitions from inactive toactive, techniques disclosed herein may save the current ringer volumeof a telephone before changing the ringer volume. In response to atransition of the logic module from active to inactive, such saved statemay be restored to the system from which the state was saved, such as byrestoring the telephone ringer volume to its saved state. As anotherexample, when a logic module transitions from inactive to active,techniques disclosed herein may terminate an email client if the logicmodule specifies that transmission of email messages is to be blocked.In response to a transition of the logic module from active to inactive,such saved state may be restored by launching the email client that wasterminated.

Examples of state that may be saved in response to a transition of alogic module or profile from inactive to active, and restored inresponse to a transition of a communication mode profile from active toinactive, include but are not limited to: ringer volume, ringer tone,automatic forwarding of voice calls to voicemail, enabled/disabled stateof user interface elements (e.g., buttons, menus, and menu items), emailsend/receive schedule, enabled/disabled state of automatic emailsending/receiving, and manifestation of receipt of messages.

As used herein, “manifesting” data refers to providing output, to auser, that represents such data. Such output may take any form, such asa visual form and/or an auditory form. For example, such output mayinclude any one or more of the following in any combination: text,graphics, images, video, and audio. As this description makes clear, anyoutput described herein as being “manifested,” may, for example, solelyinclude text, solely include graphics, solely include video, or solelyinclude audio.

Having described message control profiles in general, techniques willnext be described for using message control profiles to controltransmission, reception, and notification of messages. First, however,the meaning of the term “communication mode” as used herein will bedescribed.

In general, the “communication mode” of a particular message refers toany feature(s) of the method by which the message is transmitted (sentand/or received). A particular message having a particular communicationmode is transmissible via the particular communication mode. Forexample, a message may be transmissible via a communication mode becausethe message is formatted in a manner that makes the message adapted fortransmission via the communication mode (e.g., formatted according to aprotocol for transmitting messages via the communication mode). If amessage actually is transmitted via a communication mode, then themessage necessarily is transmissible via the communication mode. Amessage need not, however, actually be transmitted via a communicationmode to be transmissible via that communication mode. For example, amessage that is formatted according to a protocol for transmittingmessages via the communication mode is transmissible via thecommunication mode even if the message is deleted or otherwise blockedfrom being transmitted via the communication mode.

Terms such as “transmit” and “transmission” as applied to messagesherein include sending and/or receiving messages. For example,“transmitting a message” includes solely sending a message, solelyreceiving a message, and both sending and receiving a message.Similarly, “transmitting messages” includes solely sending messages,solely receiving messages, and a combination of sending some messagesand receiving other messages. Transmitting a message may includetransmitting a message from one communication device to another over anetwork and/or transmitting a message within one communication device,e.g., from one application executing on the communication device toanother application executing on the communication device.

The following examples of communication modes are exemplary and notexhaustive.

A communication mode may be defined by reference to one or morecategories of message transmission. For example, the followingcategories are examples of communication modes: email, text message,live voice call, fax, and voice message. Because such modes arecategories, a single mode may include, for example:

-   -   messages transmitted via multiple different messaging protocols        (e.g., IMAP and POPS in the case of email messages);    -   messages sent and messages received;    -   messages transmitted by multiple applications; and    -   messages transmitted by multiple devices.

Therefore, for example, if the communication mode specified by aparticular communication mode profile is an “email” communication modeand the action associated with that communication mode profile is“block,” then the message control system may apply that communicationmode profile by blocking all email messages, regardless of the protocolby which they are transmitted (or attempted to be transmitted),regardless of whether they are sent or received, regardless of theapplication by which they are transmitted, and regardless of the deviceby which they are transmitted.

As another example, a communication mode may be defined by reference toone or more messaging protocols. For example, the IMAP email protocol isan example of a communication mode. Therefore, if the communication modespecified by a particular communication mode profile is “IMAP email,”then the action specified by that communication mode profile will beperformed only in connection with email received using the IMAP emailprotocol, and not, for example, email received using other emailprotocols. Messaging protocols that may define communication modesaccording to embodiments of the present invention include any messagingprotocols at any layer of the OSI (Open Systems Interconnection)seven-layer model. Examples of messaging protocols that may definecommunication modes according to embodiments of the present inventioninclude, but are not limited to, Ethernet, GFP (Generic FramingProcedure), OTN (Optical Transport Network), IP (Internet Protocol), TCP(Transmission Control Protocol), UDP (User Datagram Protocol), HTTP(Hypertext Transfer Protocol), IMAP (Internet Message Access Protocol),IRC (Internet Relay Chat), POP3 (Post Office Protocol Version 3), andSMTP (Simple Mail Transfer Protocol), VoIP (Voice over InternetProtocol).

As another example, a communication mode may be defined by reference toone or more messaging services, such as SMS (Short Message Service), MMS(Multimedia Messaging Service), and EMS (Enhanced Messaging Service).

As another example, a communication mode may be defined by reference toa direction of transmission (i.e., send or receive). For example, if thecommunication mode specified by a particular communication mode profileis “receive,” then the action specified by that communication modeprofile will be performed in connection with received messages but notin connection with sent messages. Note that, for example, such a“receive” communication mode may include messages in multiple categories(e.g., email messages, text messages, and voice calls), transmittedusing multiple protocols, and transmitted using multiple devices.

As another example, a communication mode may be defined by reference toone or more communication accounts. For example, messages transmissiblevia a first email account may be transmissible via a first communicationmode, messages transmissible via a second email account may betransmissible via a second communication mode, and messagestransmissible via a first text messaging account may be transmissiblevia a third communication mode.

As another example, a communication mode may be defined by reference toone or more types of message content, such as any of the following:text, image, video, and audio. Such content types may be furtherdivided. For example, audio content may be divided into voice andnon-voice content, each of which may define a separate mode.

Similarly, a communication mode may be defined by reference to one ormore types of content manifestation, by which is meant the type ofcontent that is used to manifest a particular message. For example, avoice call that is manifested by playing the audio through a speaker ismanifested using an “audio” type of content. Similarly, a text messagethat is converted into speech by a text-to-speech engine is alsomanifested using an “audio” type of content, even though the textmessage itself has a “text” type of content.

Similarly, a communication mode may be defined by reference to theapplication that generated, sent, received, and/or manifested a message.For example, a communication mode may be defined by reference to one ormore named applications (e.g., Microsoft Outlook, Mozilla FireFox,Facebook), one or more application types (e.g., email client, webbrowser, text messaging client), and/or the installation/executionlocation of the application (e.g., installed locally on the user'scomputer or installed and executing remotely, such as in the case ofcloud-based applications, such as Facebook and Twitter). The definitionof such a communication mode may encompass any one or more ofgenerating, sending, receiving, and manifesting messages. For example, acommunication mode may be defined to include messages generated, sent,received, and manifested by a particular named application (e.g.,Microsoft Outlook), or only to include messages received by such anapplication but not to messages generated, sent, or manifested by suchan application.

Any of the characteristics of communication modes described above may becombined with each other in any way. For example, a communication modemay be defined by reference to a message category (e.g., email) andtransmission direction (e.g., receive) to define a communication modethat encompasses “received email.”

The description herein refers to “detecting” a message. Such detectionmay include, for example, any one or more of the following: detection ofan instruction to send the message, detection of an attempt to send themessage, detection of the message in the process of being sent,detection that the message has been sent, detection of a scheduled timeto send the message, detection of an instruction to receive the message,detection of an attempt to receive the message, detection of the messagein the process of being received, detection that the message has beenreceived, and detection of a scheduled time to receive the message.

A “communication device” may be any device that is capable of performingany one or more of the following functions: transmitting messages,receiving messages, and providing notifications of messages. Examples ofcommunication devices include desktop computers, laptop computers,tablet computers, cellular telephones (including smartphones), andpersonal digital assistants (PDAs), and combinations thereof.

Embodiments of the present invention may be applied to messages,notifications of messages, or both. A notification of a message is anyoutput derived from a message that is intended to provide informationabout the message. For example, when an email client displays thesubject line of an email message but not the remainder of the emailmessage, the displayed subject line is an example of a notification ofthe email message. In this example, the notification is output to auser, but this is not required. Instead, for example, a notification maybe transmitted between two computing devices or two computer programs. Anotification of a message may contain some or all of the content of themessage. A notification of a message may contain information that isderived from, but not contained within the content of the message. Anotification may be manifested in any of the ways disclosed herein. Anyof the actions disclosed herein may be performed on notifications. Anotification may itself be a message.

It is to be understood that although the invention has been describedabove in terms of particular embodiments, the foregoing embodiments areprovided as illustrative only, and do not limit or define the scope ofthe invention. Various other embodiments, including but not limited tothe following, are also within the scope of the claims. For example,elements and components described herein may be further divided intoadditional components or joined together to form fewer components forperforming the same functions.

Any of the functions disclosed herein may be implemented using means forperforming those functions. Such means include, but are not limited to,any of the components disclosed herein, such as the computer-relatedcomponents described below.

The techniques described above may be implemented, for example, inhardware, one or more computer programs tangibly stored on one or morenon-transitory computer-readable media, firmware, or any combinationthereof. The techniques described above may be implemented in one ormore computer programs executing on a programmable computer including aprocessor, a storage medium readable by the processor (including, forexample, volatile and non-volatile memory and/or storage elements), atleast one input device, and at least one output device. Program code maybe applied to input entered using the input device to perform thefunctions described and to generate output. The output may be providedto one or more output devices.

Terms such as “computer,” “computing device,” and “communicationdevice,” as used herein refer, for example, to desktop computers, laptopcomputers, cellular telephones and smartphones, personal digitalassistants (PDAs), and tablet computers.

Each computer program within the scope of the claims below may beimplemented in any programming language, such as assembly language,machine language, a high-level procedural programming language, or anobject-oriented programming language. The programming language may, forexample, be a compiled or interpreted programming language.

Each such computer program may be implemented in a computer programproduct tangibly embodied in a machine-readable storage device forexecution by a computer processor. Method steps of the invention may beperformed by a computer processor executing a program tangibly embodiedon a computer-readable medium to perform functions of the invention byoperating on input and generating output. Suitable processors include,by way of example, both general and special purpose microprocessors.Generally, the processor receives instructions and data from a read-onlymemory and/or a random access memory. Storage devices suitable fortangibly embodying computer program instructions include, for example,all forms of non-volatile memory, such as semiconductor memory devices,including EPROM, EEPROM, and flash memory devices; magnetic disks suchas internal hard disks and removable disks; magneto-optical disks; andCD-ROMs. Any of the foregoing may be supplemented by, or incorporatedin, specially-designed ASICs (application-specific integrated circuits)or FPGAs (Field-Programmable Gate Arrays). A computer can generally alsoreceive programs and data from a storage medium such as an internal disk(not shown) or a removable disk. These elements will also be found in aconventional desktop or workstation computer as well as other computerssuitable for executing computer programs implementing the methodsdescribed herein, which may be used in conjunction with any digitalprint engine or marking engine, display monitor, or other raster outputdevice capable of producing color or gray scale pixels on paper, film,display screen, or other output medium.

Embodiments of the present invention have a variety of advantages. Forexample, the ability of modern computing devices to engage inmultitasking has a variety of benefits. For example, the user of amultitasking device can use that device to perform multiple tasks,without the need to purchase or use multiple devices. The ability of adevice to multitask, however, can generate interruptions and otherdistractions that can decrease the user's productivity in connectionwith the activity in which the user currently is engaged. One benefit ofembodiments of the present invention is that they enable the user tofocus on one activity at a time, free from interruptions and otherdistractions. Such embodiments may, therefore, increase the user'sproductivity.

Embodiments of the present invention need not, however, limit the userto using a multitasking device to perform only one task. Instead,embodiments of the present invention may limit the user to using themultitasking device to perform only one task at a time, while stillallowing the user to switch from one task to another over time. As aresult, the user may still obtain the benefit of a single device that iscapable of performing multiple tasks by using such a device to performthose tasks sequentially. While the user is using the device to performany particular task as part of an activity in which the user is engaged,the user may remain focused on that activity, even if the usersubsequently uses the device to perform a different task.

What is claimed is:
 1. A method performed by at least one computerprocessor, the method for use with a first device, the methodcomprising: (A) determining that the first device is performing a firsttask, wherein the first task comprises at least one of transmitting,manifesting, and composing a first message transmissible via a firstcommunication mode, wherein the first communication mode comprises oneof an email communication mode, a text message communication mode, and avoice call communication mode, wherein the first device includes a firstmodule for performing the first task and a second module for performinga second task, wherein the second task comprises at least one oftransmitting, manifesting, and composing a second message transmissiblevia a second communication mode, wherein the second communication modecomprises one of the email communication mode, the text messagecommunication mode, and the voice call communication mode, wherein thefirst communication mode differs from the second communication mode; (B)in response to the determination of (A), preventing the first devicefrom performing the second task while the first device is performing thefirst task; (C) determining that the first device is performing thesecond task; and (D) in response to the determination of (C), preventingthe first device from performing the first task while the first deviceis performing the second task.
 2. The method of claim 1, wherein thefirst task comprises manifesting the first message, wherein the secondtask comprises manifesting the second message, and wherein preventingthe first device from performing the second task while the first deviceis performing the first task comprises preventing the first device frommanifesting the second message while the first device manifests thefirst message.
 3. The method of claim 1, wherein the first taskcomprises manifesting the first message, wherein the second taskcomprises manifesting a notification of the second message, and whereinpreventing the first device from performing the second task while thefirst device is performing the first task comprises preventing the firstdevice from manifesting the notification of the second message while thefirst device manifests the first message.
 4. The method of claim 1,wherein the first task comprises manifesting the first message, whereinthe second task comprises composing the second message, and whereinpreventing the first device from performing the second task while thefirst device is performing the first task comprises preventing the firstdevice from composing the second message while the first devicemanifests the first message.
 5. The method of claim 1, wherein the firsttask comprises composing the first message, wherein the second taskcomprises manifesting the second message, and wherein preventing thefirst device from performing the second task while the first device isperforming the first task comprises preventing the first device frommanifesting the second message while the first device composes the firstmessage.
 6. The method of claim 1, wherein the first task comprisescomposing the first message, wherein the second task comprisesmanifesting a notification of the second message, and wherein preventingthe first device from performing the second task while the first deviceis performing the first task comprises preventing the first device frommanifesting the notification of the second message while the firstdevice composes the first message.
 7. The method of claim 1, wherein thefirst task comprises composing the first message, wherein the secondtask comprises composing the second message, and wherein preventing thefirst device from performing the second task while the first device isperforming the first task comprises preventing the first device fromcomposing the second message while the first device composes the firstmessage.
 8. The method of claim 1, wherein (B) further comprises, inresponse to the determination of (A), preventing a second device fromperforming the second task while the first device is performing thefirst task, wherein the second device differs from the first device. 9.The method of claim 1: wherein the first device further comprises athird module for performing a third task, wherein the third taskcomprises at least one of transmitting, manifesting, and composing athird message transmissible via a third communication mode, wherein thethird communication mode comprises at least one of the emailcommunication mode, the text message communication mode, and the voicecall communication mode, wherein the third task differs from the firstand second tasks; and wherein (B) comprises, in response to thedetermination of (A), preventing the first device from performing thesecond and third tasks while the first device is performing the firsttask.
 10. The method of claim 1, further comprising: (E) receivingcontext data; (F) determining that a predetermined condition issatisfied by the context data; and (G) allowing the first device toperform the first task in response to determining that the predeterminedcondition is satisfied.
 11. The method of claim 10: wherein (E)comprises receiving output, representing a time, from a time sensor; andwherein (F) comprises determining that the predetermined condition issatisfied by the output received from the time sensor.
 12. The method ofclaim 1, further comprising: (E) receiving user input; and (F) allowingthe first device to perform the first task in response to the userinput.
 13. The method of claim 1, wherein preventing the first devicefrom performing the second task comprises disabling the second module.14. A non-transitory computer-readable medium comprising computerprogram instructions tangibly stored on the non-transitorycomputer-readable medium, wherein the instructions are executable by atleast one computer processor to perform a method for use with a firstdevice, the method comprising: (A) determining that the first device isperforming a first task, wherein the first task comprises at least oneof transmitting, manifesting, and composing a first messagetransmissible via a first communication mode, wherein the firstcommunication mode comprises one of an email communication mode, a textmessage communication mode, and a voice call communication mode, whereinthe first device includes a first module for performing the first taskand a second module for performing a second task, wherein the secondtask comprises at least one of transmitting, manifesting, and composinga second message transmissible via a second communication mode, whereinthe second communication mode comprises one of the email communicationmode, the text message communication mode, and the voice callcommunication mode, wherein the first communication mode differs fromthe second communication mode; (B) in response to the determination of(A), preventing the first device from performing the second task whilethe first device is performing the first task; (C) determining that thefirst device is performing the second task; and (D) in response to thedetermination of (C), preventing the first device from performing thefirst task while the first device is performing the second task.
 15. Thenon-transitory computer-readable medium of claim 14, wherein the firsttask comprises manifesting the first message, wherein the second taskcomprises manifesting the second message, and wherein preventing thefirst device from performing the second task while the first device isperforming the first task comprises preventing the first device frommanifesting the second message while the first device manifests thefirst message.
 16. The non-transitory computer-readable medium of claim14, wherein the first task comprises manifesting the first message,wherein the second task comprises manifesting a notification of thesecond message, and wherein preventing the first device from performingthe second task while the first device is performing the first taskcomprises preventing the first device from manifesting the notificationof the second message while the first device manifests the firstmessage.
 17. The non-transitory computer-readable medium of claim 14,wherein the first task comprises manifesting the first message, whereinthe second task comprises composing the second message, and whereinpreventing the first device from performing the second task while thefirst device is performing the first task comprises preventing the firstdevice from composing the second message while the first devicemanifests the first message.
 18. The non-transitory computer-readablemedium of claim 14, wherein the first task comprises composing the firstmessage, wherein the second task comprises manifesting the secondmessage, and wherein preventing the first device from performing thesecond task while the first device is performing the first taskcomprises preventing the first device from manifesting the secondmessage while the first device composes the first message.
 19. Thenon-transitory computer-readable medium of claim 14, wherein the firsttask comprises composing the first message, wherein the second taskcomprises manifesting a notification of the second message, and whereinpreventing the first device from performing the second task while thefirst device is performing the first task comprises preventing the firstdevice from manifesting the notification of the second message while thefirst device composes the first message.
 20. The non-transitorycomputer-readable medium of claim 14, wherein the first task comprisescomposing the first message, wherein the second task comprises composingthe second message, and wherein preventing the first device fromperforming the second task while the first device is performing thefirst task comprises preventing the first device from composing thesecond message while the first device composes the first message. 21.The non-transitory computer-readable medium of claim 14, wherein (B)further comprises, in response to the determination of (A), preventing asecond device from performing the second task while the first device isperforming the first task, wherein the second device differs from thefirst device.
 22. The non-transitory computer-readable medium of claim14: wherein the first device further comprises a third module forperforming a third task, wherein the third task comprises at least oneof transmitting, manifesting, and composing a third messagetransmissible via a third communication mode, wherein the thirdcommunication mode comprises at least one of the email communicationmode, the text message communication mode, and the voice callcommunication mode, wherein the third task differs from the first andsecond tasks; and wherein (B) comprises, in response to thedetermination of (A), preventing the first device from performing thesecond and third tasks while the first device is performing the firsttask.
 23. The non-transitory computer-readable medium of claim 14,wherein the method further comprises: (E) receiving context data; (F)determining that a predetermined condition is satisfied by the contextdata; and (G) allowing the first device to perform the first task inresponse to determining that the predetermined condition is satisfied.24. The non-transitory computer-readable medium of claim 23: wherein (E)comprises receiving output, representing a time, from a time sensor; andwherein (F) comprises determining that the predetermined condition issatisfied by the output received from the time sensor.
 25. Thenon-transitory computer-readable medium of claim 14, wherein the methodfurther comprises: (E) receiving user input; and (F) allowing the firstdevice to perform the first task in response to the user input.
 26. Thenon-transitory computer-readable medium of claim 14, wherein preventingthe first device from performing the second task comprises disabling thesecond module.